Systems and methods for display device and sensor electronics unit communication

ABSTRACT

Methods and apparatus are provided for communication among display devices and sensor electronics unit in an analyte monitoring system. The analyte monitoring system may include a sensor that is configured to perform measurements indicative of analyte levels. The sensor may be communicatively coupled to the sensor electronics unit. The sensor electronics unit may be configured to transmit data indicative of analyte levels to the display devices using one or more communication protocols. Furthermore, the sensor electronics unit may be configured to operate in multiple modes, and switch between the modes in response to commands received from the display devices. Related systems, methods, and articles of manufacture are also described.

INCORPORATION BY REFERENCE TO RELATED APPLICATION

Any and all priority claims identified in the Application Data Sheet, orany correction thereto, are hereby incorporated by reference under 37CFR 1.57. This application is a continuation of U.S. application Ser.No. 16/556,144, filed Aug. 29, 2019, which is a continuation of U.S.application Ser. No. 15/471,374, filed Mar. 28, 2017, now U.S. Pat. No.10,561,349, which claims the benefit of U.S. Provisional Application No.62/315,976, filed on Mar. 31, 2016. Each of the aforementionedapplications is incorporated by reference herein in its entirety, andeach is hereby expressly made a part of this specification.

FIELD

The present application relates generally to systems and methods forcommunications between a sensor electronics unit and a display device ofan analyte monitoring system.

BACKGROUND

Analyte monitors can be configured to mount on tissue to detect analytesin a sensing area. For example, and without limitation, analyte monitorscan include sensors that measure the concentration of glucose, lactate,cholesterol, hemoglobin, and/or other blood or bodily fluidconstituents.

In some cases, persons with diabetes mellitus (also known as diabetes)can use an analyte monitor. Diabetes is a disorder in which the pancreasof a person may not create sufficient insulin, such as in the case ofType I diabetes, and/or in which insulin may not be effective for aperson, such as is in the case of Type II diabetes. In a diabetic state,a victim can suffer from high blood sugar, which can cause an array ofphysiological derangements, such as kidney failure, skin ulcers, orbleeding into the vitreous of the eye, which can be associated with thedeterioration of small blood vessels. A hypoglycemic reaction, such aslow blood sugar, can be induced by an inadvertent overdose of insulin,or after a normal dose of insulin or glucose-lowering agent accompaniedby extraordinary exercise or insufficient food intake.

In some cases, a diabetic can carry an analyte monitor such as aself-monitoring blood glucose (“SMBG”) monitor, which typically canutilize uncomfortable finger pricking methods. Due to the lack ofcomfort and/or convenience, a diabetic typically measures his or herglucose level only two to four times per day. Unfortunately, these timeintervals can be spread so far apart that the diabetic would likely findout too late that he/she has a hyperglycemic or hypoglycemic condition,which can sometimes cause dangerous side effects. In fact, it is notonly unlikely that a diabetic would take a timely SMBG value, butadditionally, the diabetic would likely not know if his/her bloodglucose value is rising or falling based on conventional methods.

Consequently, a variety of analyte monitors are being developed toinclude non-invasive, transdermal (e.g., transcutaneous), and/orimplantable electrochemical sensors for continuously detecting and/orquantifying blood glucose values. These, as well as other types ofdevices, generally transmit raw or processed data to remote devices,which can include a display, to allow presentation of information to auser hosting the sensor.

SUMMARY

Any of the features of aspects specified herein are applicable to allother aspects and implementations identified herein. Moreover, any ofthe features of an aspect is independently combinable, partly or whollywith other aspects described herein in any way, e.g., one, two, or threeor more aspects may be combinable in whole or in part. Further, any ofthe features of an aspect may be made optional to other aspects. Anyaspect of a method can be performed by a system or apparatus of anotheraspect, and any aspect or of a system can be configured to perform amethod of another aspect.

In some implementations, a plurality of communication protocols can beused for communication between a sensor electronics unit and one or moredisplay devices. The communication between the sensor electronics unitcan be based on wired and/or wireless communication protocols, whichwill be discussed later in this disclosure with reference to FIGS. 3-4,as well as elsewhere throughout this disclosure. For example, andwithout limitation, a first communication protocol can utilize radiotransmission, such as BLUETOOTH®, or Bluetooth Low Energy (BLE) wirelesscommunication protocol, which uses a radio transmission frequency range2.4 to 2.485 GHz. A second communication protocol can utilize a radiofrequency (“RF”) field, such as near field communication (“NFC”) orradio frequency identification (“RFID”). NFC can be an RF field with a13.56 MHz frequency. RFID can operate in a range of frequency bands,such as, without limitation, 120-150 kHz, 13.56 MHz, 433 MHz, 865-868MHz, 902-928 MHz, 2450-5800 MHz, 3.1-10 GHz.

In some implementations, the second communication protocol can be usedby a display device to communicate with a sensor electronics unit. Insome cases, these communications can include commands/requests,transmissions of data, and/or other communications.

In some implementations, the display device can utilize the secondcommunication protocol to cause the sensor electronics unit to performone or more actions. In some cases, these actions can be combined in anaction queue. Accordingly, the actions described in variousimplementations in this disclosure can be combined and performed in asequence of actions. These various actions, and their functional units,will be discussed later in this disclosure with reference to FIGS. 5C,6A-B, as well as elsewhere throughout this disclosure.

In some implementations, one action can be a wake action, where thedisplay device uses the second communication protocol to sendcommands/requests and/or data to wake up a sensor electronics unit froma shelf mode, idle mode, and/or any low power mode. In some cases, afterthe sensor electronics unit wakes, it can pair and communicate using thefirst communication protocol with the display device that was used towake the sensor electronics unit. Similarly, the second communicationprotocol can be used to change the mode of operation of the sensorelectronics unit, such as changing it to shelf mode, idle mode, lowpower mode, normal mode, high speed mode, and/or any mode that may bedesirable for the sensor electronics unit.

In some embodiments, an analyte level monitoring system including ananalyte sensor for measuring analyte levels and communicatively coupledto a sensor electronics unit is provided. The sensor electronics unit isconfigured to receive analyte measurement data from the sensor and maybe further configured to process the data to calculate estimated analytevalues based on the measurement data. The sensor electronics unit isalso configured to communicate with a display device using a pluralityof communication protocols and to operate in a plurality of operationalmodes. For example, and without limitation, modes of operation mayinclude a normal power mode and a low power mode. The display device isconfigured to communicate commands to the sensor electronics unit usingat least one of the plurality of communication protocols. For instancethe commands may include one or more commands which, upon receipt by thesensor electronics unit, cause the sensor electronics unit to switchfrom a low power mode, such as a storage mode, to a normal power modeand/or wirelessly connect to the display device using a communicationprotocol different from the one used to communicate the command.Alternatively, the sensor electronics unit may switch from a normalpower mode to a low power mode and/or terminate a connection forcommunication with the display device using a first communicationprotocol in response to a command communicated using a secondcommunication protocol. The sensor electronics unit may communicate dataindicative of analyte levels, such as analyte measurement data orestimated analyte values, to the display device using at least one ofthe plurality of communication protocols, for instance while operatingin the normal power mode. In some of these embodiments, the displaydevice is configured to process analyte measurement data to calculateestimated analyte values.

In other embodiments, an analyte monitoring system comprises an analytesensor for measuring analyte levels and communicatively coupled to asensor electronics unit. The sensor electronics unit is configured toreceive analyte measurement data from the sensor and may be furtherconfigured to process the data to calculate estimated analyte valuesbased on the measurement data. The sensor electronics unit is alsoconfigured to communicate with a display device using a plurality ofcommunication protocols. The sensor electronics unit may communicateanalyte measurement data or estimated analyte values to the displaydevice using a first communication protocol. In some of theseembodiments, the display device is configured to process analytemeasurement data to calculate estimated analyte values. The displaydevice is also configured to communicate commands to the sensorelectronics unit using a second communication protocol. For instance,upon receipt of the commands by the sensor electronics unit, the sensorelectronics unit may cease to perform analyte measurements, and furthercease to transmit analyte measurement data or estimated analyte values.

In some embodiments, an analyte level monitoring system including ananalyte sensor for measuring analyte levels and communicatively coupledto a sensor electronics unit is provided. The sensor electronics unit isconfigured to receive analyte measurement data from the sensor and maybe further configured to process the data to calculate estimated analytevalues based on the measurement data. The sensor electronics unit isalso configured to communicate with a display device using a pluralityof communication protocols. The sensor electronics unit may communicateanalyte measurement data or estimated analyte values to the displaydevice at a predefined time using a first communication protocol. Thesensor electronics unit may further be configured to communicate analytemeasurement data or estimated analyte values from before the predefinedtime to the display device using a second communication protocol. Insome of these embodiments, the display device is configured to processanalyte measurement data to calculate estimated analyte values.

In other embodiments, an analyte monitoring system comprises an analytesensor for measuring analyte levels and communicatively coupled to asensor electronics unit. The sensor electronics unit is configured toreceive analyte measurement data from the sensor and may be furtherconfigured to process the data to calculate estimated analyte valuesbased on the measurement data. The sensor electronics unit is alsoconfigured to communicate with a display device using a plurality ofcommunication protocols. The sensor electronics unit may communicateanalyte measurement data or estimated analyte values to the displaydevice using a first communication protocol. In some of theseembodiments, the display device is configured to process analytemeasurement data to calculate estimated analyte values. The displaydevice is also configured to communicate commands to the sensorelectronics unit using a second communication protocol. For instance thecommands may include one or more instructions which, upon receipt by thesensor electronics unit, cause the sensor electronics unit to transmitanalyte measurement data or estimated analyte values using the firstcommunication protocol in response to the data request command sentusing the second communication protocol. Alternatively a portion of theanalyte data or values may be communicated using the first communicationprotocol, and another portion of the analyte data or values may becommunicated using a different communication protocol.

In some implementations, one action can be a calibrate action, where thedisplay device uses the second communication protocol to sendcommands/requests and/or data to transmit calibration data to the sensorelectronics unit and calibrate the sensor electronics unit. Thiscalibration data can include data obtained by a user through fingerpricking and entered onto a display device. The calibration data can beused by the sensor electronics unit to calibrate its calibrationfunction that converts the raw measurements (e.g., currents, voltages,resistances, gate logic, etc.) of an analyte sensor into data indicativeof analyte measurements, such as estimated glucose values (“EGVs”),estimated blood glucose levels, blood glucose levels, and/or any otheranalyte measurement or estimation of an analyte measurement.

In some implementations, one action can be a clone action where thedisplay device can use the second communication protocol to sendcommands/requests and/or data that clones the sensor electronics unit.For example, and without limitation, two sensor electronics units can beused in a cloning action. The display device can send commands/requeststo a first sensor electronics unit using the second communicationprotocol to send a portion or all of the stored data of the first sensorelectronics unit (e.g., white lists, bonding lists, calibration data,analyte measurements, raw sensor measurements, etc.) to the displaydevice over the first communication protocol or the second communicationprotocol. The display device can then use the second communicationprotocol to then initiate a transfer of the data it obtained from thefirst sensor electronics unit to the second sensor electronics unit.

In some implementations, one action can be a retrieve data action wherethe display device can use the second communication protocol to sendcommands/requests and/or data that causes the sensor electronics unit tosend data to the display device using the first communication protocoland/or the second communication protocol. For example, and withoutlimitation, NFC-capable or RFID-capable display devices may alter thenormal establishment of communications, such as scheduled communicationsor communications following a particular timing as described later inthis disclosure with reference to FIG. 7A-E and elsewhere throughoutthis disclosure. For example, and without limitation, a user may wish tohave a sensor electronics unit transmit sensor information prior to ascheduled transmission. This transmission can be due to the user/hostfeeling the onset of a hypoglycemic condition, or the user may wish tohave a backlog of sensor data transmitted in a bulk transfer to adisplay device.

In some implementations, one action can be a set white/bonding listaction where the display device uses the second communication protocolto send commands/requests and/or data that sets, adjusts, and/ormanipulates the white list or bonding list of the first communicationprotocol in the sensor electronics unit. White lists and bonding listswill be discussed in more detail later in this disclosure with referenceto FIGS. 5C, 6A-B, 9A-F, as well as elsewhere throughout thisdisclosure. This action can include adding display devices to the whitelist or bonding list, removing display devices from the white list orbonding list, and/or rearranging the white list and/or bonding list. Insome implementations, adding the display device can transmit over thesecond communication protocol command(s) that add that display device tothe sensor electronic unit's white list for the first communicationprotocol, where the command(s) can also designate the position of thedisplay device, and other display devices, on that white list, and canshift other display devices off the white list.

In some implementations, one action can be to start or stop a sensorsession, where the display device uses the second communication protocolto send commands/requests and/or data that causes the sensor electronicsunit to start or stop sensor measurements and/or transmissions.

In some implementations, a plurality of communication protocols (e.g.,the first and second communication protocol) can be used to send dataand/or commands. For example, and without limitation, certain types ofcommunications can be transmitted over the first communication protocoland certain types of communications can be transmitted over the secondcommunication protocol. By way of illustration, and without limitation,all commands can be sent over the second communication protocol and alldata can be sent over the first communication protocol. In someimplementations, communications can be split between the firstcommunication protocol and the second communication protocol. Forexample, and without limitation, encrypted data/information can be sentover one communication protocol whereas the decryption key and/or othersecurity information can be sent over another communication protocol sothat a display device uses both communication protocols to be able toread communications from a sensor electronics unit. In someimplementations, communications can be split between a pluralitycommunication protocols so that a complete message comprisesdata/information from the plurality of communication protocols.

In some implementations, a sensor electronics unit can adjustcommunication protocols based on battery life. For example, and withoutlimitation, the second communication protocol can be used to recoverdata from a dead and/or low power sensor electronics unit. In somecases, the sensor electronics unit can cease data measurements and/ortransmission when the battery life falls below a predeterminedthreshold. One or more communication protocols (e.g., the secondcommunication protocol) may then be used to power the sensor electronicsmodule and further recover the data stored in the sensor electronicsmodule. In some cases, the sensor electronics unit can load the dataonto a passive tag when its battery life falls below a predeterminedthreshold.

In some cases, a display device can use NFC to power and/or initiate thecommunication from a sensor electronics unit to the display device viaradio transmission (e.g. using a BLUETOOTH® or BLE wireless protocol).Such may be desirable when the sensor electronics unit has low batterylife or no battery life. This can be used by a health practitioner toprocess patient data and/or by any user to pull data off a dying or deadsensor electronics unit, or in cases where there is a malfunction of thesensor electronics unit.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed aspects will hereinafter be described in conjunction withthe appended drawings, provided to illustrate and not to limit thedisclosed aspects, wherein like designations denote like elements.Details of one or more implementations of the subject matter describedin this specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages will becomeapparent from the description, the drawings, and the claims. Note thatthe relative dimensions of the following figures may not be drawn toscale.

FIG. 1A is a diagram depicting an example continuous analyte monitoringsystem having a sensor electronics unit, a sensor, and a plurality ofdisplay devices that can be connected to the sensor electronics unit.

FIG. 1B illustrates an example flow chart showing an example initiationof a sensor electronics unit from manufacturing to use by a user.

FIG. 1C illustrates an example display device and sensor electronicsunit communicating with two different communication channels.

FIG. 2A illustrates a block diagram of an example system where a sensorelectronics unit is communicatively coupled to a plurality of displaydevices using a plurality of communication channels.

FIG. 2B illustrates an example system where an example sensorelectronics unit is communicatively coupled to two example displaydevices.

FIG. 3 illustrates a functional block diagram of an example sensorelectronics unit.

FIG. 4A illustrates a functional block diagram of an example displaydevice.

FIG. 4B is an example advertising/connection sequence between an examplesensor electronics unit and an example display device.

FIG. 5A illustrates example ranges of example communication protocols ofan example sensor electronics unit, where each communication protocolhas a different range.

FIG. 5B illustrates example ranges of example communication protocols ofan example display device, where each communication protocol has adifferent range.

FIG. 5C illustrates an example functional block diagram illustratingexample functional units of an example display device.

FIG. 6A illustrates an example interface where a user can select NFCfunctionality from an example display device.

FIG. 6B illustrates an example interface for performing actions in anexample action queue over NFC.

FIG. 6C illustrates an example timing diagram where an RF fieldcommunication protocol is used to wake an example sensor electronicsunit from a low power mode.

FIG. 6D illustrates an example flow chart illustrating the process ofwaking up an example sensor electronics unit using an RF fieldcommunication protocol.

FIG. 6E illustrates an example timing diagram of an example sensorelectronics unit that is put into a low power mode.

FIG. 7A illustrates an example timing diagram of an example firstcommunication protocol for an example sensor electronics unit.

FIG. 7B illustrates an example timing diagram of an example sensorelectronics unit showing signal processing that can occur between thecommunications of the first communication protocol of FIG. 7A.

FIG. 7C illustrates an example transmission from an example sensorelectronics unit using a second communication protocol to initiate acommunication using the first communication protocol from the exampletiming diagram of FIG. 7B.

FIG. 7D illustrates an example timing diagram showing a transmissionover a second communication protocol that stops an example sensorsession.

FIG. 7E illustrates an example timing diagram showing the timing of atransmission over a second communication protocol that starts a sensorsession.

FIG. 8 illustrates an example flow chart showing how one communicationprotocol can be used to facilitate pairing for communication usinganother communication protocol.

FIG. 9A illustrates an example white list and example bonding list thatcan be used for pairing an example sensor electronics units and anexample display devices by using two or more communication protocols.

FIG. 9B illustrates multiple example display devices connecting to anexample sensor electronics unit using a second communication protocol asreflected in the example white list and example bonding list illustratedin FIG. 9A.

FIG. 9C illustrates an example white list and example bonding list of acommunication protocol being updated when an example sensor electronicsunit and an example display device are unpaired using the secondcommunication protocol.

FIG. 9D illustrates an example implementation where a communicationprotocol can be used to add an example display device to the examplewhite list of another communication protocol, and remove a differentexample display device from that same example white list.

FIG. 9E illustrates an example where a second communication protocol isused to reorder the example white list illustrated in FIG. 9B.

FIG. 9F illustrates an example where a second communication protocol isused to move an example display device on the example bonding list of afirst communication protocol to the example white list of that firstcommunication protocol.

FIG. 9G illustrates a graph of example sequential communication windowsfor communication between an example sensor electronics unit and anexample display devices in the example white list of FIGS. 9A-F.

DETAILED DESCRIPTION

Various aspects of the novel systems, apparatuses, and methods disclosedherein are described more fully hereinafter with reference to theaccompanying drawings. This disclosure can, however, be embodied in manydifferent forms and should not be construed as limited to any specificstructure or function presented throughout this disclosure. Rather,these aspects are provided so that this disclosure will be thorough andcomplete, and will fully convey the scope of the disclosure to thoseskilled in the art. Based on the teachings herein, one skilled in theart should appreciate that the scope of the disclosure is intended tocover any aspect of the novel systems, apparatuses, and methodsdisclosed herein, whether implemented independently of, or combinedwith, any other aspect of the disclosure. For example, an apparatus canbe implemented or a method can be practiced using any number of theaspects set forth herein. In addition, the scope of the disclosure isintended to cover such an apparatus or method that is practiced usingother structure, functionality, or structure and functionality inaddition to or other than the various aspects of the disclosure setforth herein. It should be understood that any aspect disclosed hereincan be implemented by one or more elements of a claim.

Although particular aspects are described herein, many variations andpermutations of these aspects fall within the scope of the disclosure.Although some benefits and advantages of the preferred aspects arementioned, the scope of the disclosure is not intended to be limited toparticular benefits, uses, and/or objectives. The detailed descriptionand drawings are merely illustrative of the disclosure rather thanlimiting, the scope of the disclosure being defined by the appendedclaims and equivalents thereof.

As alluded to previously, continuous monitoring of blood glucose values,one example of an analyte (discussed in greater detail below), canimprove upon conventional monitoring systems and methods by improvingcomfort and convenience, as well as lessening the chance that a person'sdeteriorating or medically critical condition goes unnoticed. Thus,various implementations described herein are directed to systems andmethods of continuous analyte monitoring and communications betweensensor electronics units and display devices.

In some implementations, a system is provided for continuous measurementof an analyte in a host that can include: a continuous analyte sensor(and/or any other sensor) configured to substantially continuouslymeasure a concentration of the analyte in the host; and a sensorelectronics unit operatively and/or communicatively coupled to thecontinuous analyte sensor to receive the analyte concentrationmeasurements and communicate them to display devices. In particular, thesensor electronics unit can include electronics configured to processdata, and/or a data stream, associated at least in part with an analyteconcentration measured by the continuous analyte sensor in order togenerate sensor information that includes raw sensor data, transformedsensor data, and/or any other sensor data or data derived therefrom,e.g., predictive or trend data. The sensor electronics unit may furtherbe configured to generate sensor information that is customized forrespective display devices, such that different display devices mayreceive sensor information modified for different display devices forpresentation to the host, a host care taker, etc.

Communications between the sensor electronics unit and one or moredisplay devices can be controlled via an advertising and communicationprotocol indicating, for example, how often and/or how long the sensorelectronics unit advertises to a display device, the order in which thesensor electronics unit advertised to a display device, etc. The sensorelectronics unit may comprise a communications unit operative inaccordance with the advertising and communication protocol, such as aradio transceiver, that effectuates such communications between thesensor electronics unit and the one or more display devices. The controleffectuated by the advertising and connection protocol can be achievedby varying or adjusting variables or parameters that can impactcommunications such as, without limitation, the timing and the order ofcommunications.

The term “analyte” as used herein is a broad term and is to be given itsordinary and customary meaning to a person of ordinary skill in the art(and is not to be limited to a special or customized meaning), andfurthermore refers without limitation to a substance or chemicalconstituent in a biological fluid (for example, blood, interstitialfluid, cerebral spinal fluid, lymph fluid or urine) that can beanalyzed. Analytes can include naturally occurring substances,artificial substances, metabolites, and/or reaction products. In someimplementations, the analyte for measurement by the sensor heads,devices, and methods is analyte. However, other analytes arecontemplated as well, including but not limited to: acarboxyprothrombin;acylcarnitine; adenine phosphoribosyl transferase; adenosine deaminase;albumin; alpha-fetoprotein; amino acid profiles (arginine (Krebs cycle),histidine/urocanic acid, homocysteine, phenylalanine/tyrosine,tryptophan); andrenostenedione; antipyrine; arabinitol enantiomers;arginase; benzoylecgonine (cocaine); biotinidase; biopterin; c-reactiveprotein; carnitine; carnosinase; CD4; ceruloplasmin; chenodeoxycholicacid; chloroquine; cholesterol; cholinesterase; conjugated 1-13hydroxy-cholic acid; cortisol; creatine kinase; creatine kinase MMisoenzyme; cyclosporin A; d-penicillamine; de-ethylchloroquine;dehydroepiandrosterone sulfate; DNA (acetylator polymorphism, alcoholdehydrogenase, alpha 1-antitrypsin, cystic fibrosis, Duchenne/Beckermuscular dystrophy, analyte-6-phosphate dehydrogenase, hemoglobin A,hemoglobin S, hemoglobin C, hemoglobin D, hemoglobin E, hemoglobin F,D-Punjab, beta-thalassemia, hepatitis B virus, HCMV, HIV-1, HTLV-1,Leber hereditary optic neuropathy, MCAD, RNA, PKU, Plasmodium vivax,sexual differentiation, 21-deoxycortisol); desbutylhalofantrine;dihydropteridine reductase; diptheria/tetanus antitoxin; erythrocytearginase; erythrocyte protoporphyrin; esterase D; fattyacids/acylglycines; free 13-human chorionic gonadotropin; freeerythrocyte porphyrin; free thyroxine (FT4); free tri-iodothyronine(FT3); fumarylacetoacetase; galactose/gal-1-phosphate;galactose-1-phosphate uridyltransferase; gentamicin; analyte-6-phosphatedehydrogenase; glutathione; glutathione perioxidase; glycocholic acid;glycosylated hemoglobin; halofantrine; hemoglobin variants;hexosaminidase A; human erythrocyte carbonic anhydrase I;17-alpha-hydroxyprogesterone; hypoxanthine phosphoribosyl transferase;immunoreactive trypsin; lactate; lead; lipoproteins ((a), B/A-1, ß);lysozyme; mefloquine; netilmicin; phenobarbitone; phenytoin;phytanic/pristanic acid; progesterone; prolactin; prolidase; purinenucleoside phosphorylase; quinine; reverse tri-iodothyronine (rT3);selenium; serum pancreatic lipase; sissomicin; somatomedin C; specificantibodies (adenovirus, anti-nuclear antibody, anti-zeta antibody,arbovirus, Aujeszky's disease virus, dengue virus, Dracunculusmedinensis, Echinococcus granulosus, Entamoeba histolytica, enterovirus,Giardia duodenalisa, Helicobacter pylori, hepatitis B virus, herpesvirus, HIV-1, IgE (atopic disease), influenza virus, Leishmaniadonovani, leptospira, measles/mumps/rubella, Mycobacterium leprae,Mycoplasma pneumoniae, Myoglobin, Onchocerca volvulus, parainfluenzavirus, Plasmodium falciparum, poliovirus, Pseudomonas aeruginosa,respiratory syncytial virus, Rickettsia (scrub typhus), Schistosomamansoni, Toxoplasma gondii, Trepenoma pallidium, Trypanosomacruzi/rangeli, vesicular stomatis virus, Wuchereria bancrofti, yellowfever virus); specific antigens (hepatitis B virus, HIV-1);succinylacetone; sulfadoxine; theophylline; thyrotropin (TSH); thyroxine(T4); thyroxine-binding globulin; trace elements; transferring;UDP-galactose-4-epimerase; urea; uroporphyrinogen I synthase; vitamin A;white blood cells; and zinc protoporphyrin. Salts, sugar, protein, fat,vitamins, and hormones naturally occurring in blood or interstitialfluids can also constitute analytes in certain implementations. Theanalyte can be naturally present in the biological fluid, for example, ametabolic product, a hormone, an antigen, an antibody, and the like.Alternatively, the analyte can be introduced into the body, for example,a contrast agent for imaging, a radioisotope, a chemical agent, afluorocarbon-based synthetic blood, or a drug or pharmaceuticalcomposition, including but not limited to insulin; ethanol; cannabis(marijuana, tetrahydrocannabinol, hashish); inhalants (nitrous oxide,amyl nitrite, butyl nitrite, chlorohydrocarbons, hydrocarbons); cocaine(crack cocaine); stimulants (amphetamines, methamphetamines, Ritalin,Cylert, Preludin, Didrex, PreState, Voranil, Sandrex, Plegine);depressants (barbiturates, methaqualone, tranquilizers such as Valium,Librium, Miltown, Serax, Equanil, Tranxene); hallucinogens(phencyclidine, lysergic acid, mescaline, peyote, psilocybin); narcotics(heroin, codeine, morphine, opium, meperidine, Percocet, Percodan,Tussionex, Fentanyl, Darvon, Talwin, Lomotil); designer drugs (analogsof fentanyl, meperidine, amphetamines, methamphetamines, andphencyclidine, for example, Ecstasy); anabolic steroids; and nicotine.The metabolic products of drugs and pharmaceutical compositions are alsocontemplated analytes. Analytes such as neurochemicals and otherchemicals generated within the body can also be analyzed, such as, forexample, ascorbic acid, uric acid, dopamine, noradrenaline,3-methoxytyramine (3MT), 3,4-Dihydroxyphenylacetic acid (DOPAC),Homovanillic acid (HVA), 5-Hydroxytryptamine (5HT), and5-Hydroxyindoleacetic acid (FHIAA).

Sensor electronics units can include electronics configured tocommunicate to and store data of sensors (e.g., analyte sensors) of auser. The sensor electronics unit can connect to display devices (e.g.,mobile devices, specialized medical receivers), or any of the otherdisplay devices described in this disclosure). In any case, displaydevices can be devices that a user can use to monitor sensormeasurements.

In some implementations, the sensor electronics unit may be configuredto search for, advertise to, and/or attempt to wirelessly communicatewith a display device, such as one from a list of display devices (e.g.,a white list). This list can be stored in memory and comprise displaydevice information that reflects, at least in part, those displaydevices or types of devices that are permitted to pair and/or bond withthe sensor electronics unit. For example, and without limitation, insome cases, only display devices or device types (e.g., model, make, orclassification of device (e.g., specialized receiver, mobile device,etc.)) on the white list can connect to a sensor electronics unit. Arequest to connect from a display device not on the white list, or froma display device whose type is not on the white list, may be ignored orrejected, and that display device may not be permitted to connect to thesensor electronics unit.

In this example, a display device on the white list may respond to anadvertising signal transmitted by the sensor electronics unit. Upon thesensor electronics unit receiving this response, the white list may beupdated with an identifier indicative of the display device. In someimplementations, a display device may be removed from the white listafter some predetermined time of inactivity, e.g., no communicationsbetween the sensor electronics unit and the display device. Another list(e.g., a bonding list) may be utilized to maintain a listing of thebonding or pairing information of display devices that can be pairedwith the sensor electronics unit. By way of illustration, and withoutlimitation, upon pairing or bonding/inclusion in the white list, thedisplay device identifier may also be stored in the bonding list. Thus,re-pairing a display device to the sensor electronics unit can then beavoided when utilizing a bonding list because the sensor electronicsunit can pull the pairing information from the bonding list. Forexample, and without limitation, if a display device is removed from thewhite list (e.g., due to some predetermined amount of inactivity,express removal, and/or the pairing of a new device) the identifier ofthat display device may still be stored in the bonding list. In thisway, the bonding list can be accessed upon the sensor electronics unitreceiving a response to an advertising signal from a display device tocheck whether or not the display device was previously bonded to thesensor electronics unit. If so, a data connection can be establishedwithout engaging in authentication.

In some implementations, the search for and/or attempted wirelesscommunication can occur in a predetermined and/or programmable order(e.g., grading and/or escalating). For example, and without limitation,if an attempt at communicating with and/or alarming a first displaydevice fails, this failure triggers an attempt to communicate withand/or alarm a second display device, and so on. It should be noted thatthe sensor electronics unit may not be tied to a single display device.Rather the sensor electronics unit can be configured to communicate witha plurality of different display devices directly, systematically,simultaneously (e.g., via broadcasting), regularly, periodically,randomly, on-demand, in response to a query, based on alerts or alarms,and/or the like.

The sensor information (e.g., data, measurements, etc.) may compriseprocessed and/or transformed sensor information that does not requireprocessing by the display device prior to display of the sensorinformation. However, some display devices may comprise softwareincluding display instructions (e.g., software programming comprisinginstructions configured to display the sensor information and optionallyquery the sensor electronics unit to obtain the sensor information)configured to enable display of the sensor information thereon. In someimplementations, the display device is programmed with the displayinstructions at the manufacturer and can include security and/orauthentication to avoid plagiarism of the display device. In someimplementations, a display device is configured to display the sensorinformation via a downloadable program (e.g., a downloadable Java Scriptvia the internet and/or a mobile application downloaded from an entitythat created and/or owns and/or licenses the app, and/or an app storesuch as from APPLE, INC. or GOOGLE INC., or other companies), such thatany display device that supports downloading of a program (for example,and without limitation, any display device that supports Java applets orthe mobile application) can be configured to display displayable sensorinformation (e.g., mobile devices, smartphones, tablets, personaldigital assistants, personal computers, and the like).

In some implementations, certain display devices may be in directwireless communication with the sensor electronics unit, althoughintermediate network hardware, firmware, and/or software can be includedwithin the direct wireless communication. In some implementations, arepeater (e.g., a BLUETOOTH® OR BLE repeater) can be used to re-transmitthe transmitted sensor information to a location farther away than theimmediate range of the telemetry module of the sensor electronics unit.In some implementations, a display device (e.g., BLUETOOTH® OR BLEdisplay device) can be used to re-transmit the transmitted sensorinformation to a display device, possibly in a different format, such asin a text message. In certain implementations, the sensor electronicsunit transmits sensor information to one or more display devices, wherethe sensor information transmitted from the sensor electronics unit isreceived by the display device without intermediate processing of thesensor information.

In some implementations, one or more display devices are configured toquery the sensor electronics unit for sensor information, where thedisplay device requests sensor information from the sensor electronicsunit in an on-demand fashion, such as, without limitation, in responseto a query. In some implementations, the sensor electronics unit can beconfigured for periodic, systematic, regular, irregular or aperiodictransmission of sensor information to one or more display devices (e.g.,every 1, 2, 5, or 10 minutes or more). In some implementations, thesensor electronics unit can be configured to transmit data packagesassociated with a triggered alert (e.g., triggered by one or more alertconditions). However, any combination of the above-described statuses ofdata transmission can be implemented with any combination of a pairedsensor electronics unit and display device(s). For example, and withoutlimitation, one or more display devices can be configured for querying asensor electronics unit database and for receiving alarm informationtriggered by one or more alarm conditions being met. Additionally, thesensor electronics unit can be configured to transmit sensor informationto one or more display devices (e.g., the same or different displaydevices as described in the previous example), where the display devicesfunction differently with regard to how they obtain sensor information.

In some implementations, as described in more detail below, a displaydevice can be configured to query/request data stored in memory in thesensor electronics unit for certain types of data content, includingdirect queries into a database in the memory of the sensor electronicsunit and/or requests for configured or configurable packages of datacontent therefrom; namely, the data stored in the sensor electronicsunit can be configurable, queryable, predetermined, and/or pre-packaged,based on the display device with which the sensor electronics unit iscommunicating. In some additional or alternative implementations, thesensor electronics unit can generate the sensor information based on thesensor electronic unit's knowledge of which display device is to receivea particular transmission. Additionally, some display devices arecapable of obtaining calibration information and wirelessly transmittingthe calibration information to the sensor electronics unit, such asthrough manual entry of the calibration information, automatic deliveryof the calibration information, and/or an integral reference analytemonitor incorporated into the display device. U.S. Patent PublicationNos. 2006/0222566, 2007/0203966, 2007/0108245, and 2005/0154271, all ofwhich are incorporated herein by reference in their entirety, describesystems and methods for providing an integral reference analyte monitorincorporated into a display device and/or other calibration methods thatcan be implemented with implementations disclosed herein.

In general, a plurality of display devices (e.g., a custom analytemonitoring device, a mobile phone, a tablet, a smart watch, a referenceanalyte monitor, a medicament delivery device, a medical device and apersonal computer) may be configured to wirelessly communicate with thesensor electronics unit. The one or more display devices can beconfigured to display at least some of the sensor information wirelesslycommunicated by the sensor electronics unit. The sensor information mayinclude, for example and without limitation, sensor data, such as rawdata and/or transformed sensor data, such as analyte concentrationvalues, rate of change information, trend information, alertinformation, sensor diagnostic information, calibration information,temperature readings or non-visual information such as sound, etc.

The features that are described throughout this disclosure have a numberof advantages as compared to presently available systems and methods.These will now generally be described. For example, there is a need inthe art for improved systems and methods of communication usingcommunication protocols between sensor electronics units and displaydevices. In some cases, the use of the communication protocol canconsume too much power, processor functionality, and/or other resourcesof a CGM system. This issue can be compounded through repetitivepairing, synchronizing, and/or handshaking procedures that may be usedin some communication protocols, such as BLUETOOTH® OR BLE. Accordingly,there is a need for improved communications that effectively utilizepower, processor functionality, and/or other resources of CGM systems.

In some cases, the repetitive pairing, synchronizing, and/or handshakingprocedures of CGM systems can also cause excessive communicationtraffic. This communication traffic can burden networks and/or drainnetwork resources (e.g., communication channels, data lines, power,processing power, etc.), such as by tying up communication channelsand/or data lines, causing interference, consuming power, utilizingprocessor time, etc. In some cases, excessive communication traffic canlead to network slowdown, network failure, and/or increased costs inrunning networks, such as more energy costs or additional hardwareutilization (e.g., processors, communication lines, cooling, etc.).Accordingly, there is a need for improved communications in CGM systems.

In particular, because certain CGM systems perform repetitivehandshaking/authentication to exchange data (e.g., EGV data) with someprotocols (e.g., radio transmission such as BLUETOOTH®), these CGMsystems can strain the battery life of sensor electronics unit. Inaddition, because multiple display devices can compete to connect withthe sensor electronics unit (e.g., during the same advertisementwindow), repetitive handshaking/authentication may lead to unwantedinterference. This interference may lead to connection failure, andeventually to unwanted data drop. Accordingly, utilizing a secondcommunication protocol (e.g., an RF field such as NFC or RFID) can allowCGM systems to more efficiently pair sensor electronics units to displaydevices on demand.

In some cases, interactions using communication protocols between sensorelectronics units and display devices can be non-intuitive and/orcumbersome for users. For example, and without limitation, a user maynavigate through multiple menus and configure multiple devices in orderto pair and/or un-pair sensor electronics units, display devices, and/orother devices that utilize a communication protocol. As anothernon-limiting example, initialization protocols, where sensor electronicsunits and/or display devices are calibrated and/or configured, canrequire navigation of multiple menus that can be cumbersome for a user.Having too many steps can detract from the user experience and/or deterusers from effectively using CGM systems and/or faithfully followingtheir medical regimen. Accordingly, there is a need for improvedcommunications in CGM systems that allow for enhanced usability.

In some cases, user authentication of a display device for a transceivercan be slow and/or cumbersome for users. However, such authenticationmay provide security for users by preventing unauthorized devices fromreceiving and/or sending data and/or commands to sensor electronicsunits. Having too many steps of an authentication scheme can detractfrom the user experience and/or also further discourage users fromeffectively using the system and/or faithfully following their medicalregimen. Accordingly, there is a need to improve user authenticationbetween display devices and sensor electronics units.

In some cases, communications over a communication protocol can becompromised and/or otherwise lead to security problems. For example, andwithout limitation, a device can steal a display devices' authenticationand/or communicate as a display device to a sensor electronics unit.Such security issues can allow an unauthorized person to receive privateinformation and/or take control of a user's CGM system, possibly causingharm. Accordingly, there is a need for advanced communication systemsand/or methods to improve security.

In some cases, some communication protocols, such as BLUETOOTH® OR BLE,use energy from the sensor electronics unit to send messages. As aresult, it can be difficult to get data from a sensor electronics unitonce the sensor electronics unit has run out of power (e.g., the sensorelectronics unit's battery has died) or there has been amalfunction/fault in the sensor electronics unit that may preventtransfer of data over radio transmission such as BLUETOOTH® OR BLE(e.g., an error in the radio protocol). Retrieving such data can bedesirable when a user has not previously accessed the data from thesensor electronics (e.g. data was note transmitted to the user's displaydevice) and/or desires an additional copy. A health practitioner mayalso desire to download this data as well in order to provide theappropriate treatment to a patient. Accordingly, there is a need forsystems and methods to extract data from sensor electronics units whenthe sensor electronics units no longer have energy to power somecommunication protocols or there has been a malfunction.

In some cases, communications can be at predefined time intervals. Forexample, a sensor electronics unit may only be able to communicate to adisplay device every 5 minutes, 10 minutes, 15 minutes, 20 minutes, orany other predefined period of time. As another example, a sensorelectronics unit may only clear devices off white lists to permit a newdevice to connect every 5 minutes, 10 minutes, 15 minutes, 20 minutes,or any other predefined period of time. A user may desire to have adisplay device pair with a sensor electronics unit, or send/receivecommunications from the display device to the sensor electronics unitoutside of the predefined period of time. Accordingly, there is a needfor systems and methods to enable communications users to pair and/orcommunicate on-demand. These and more advantages will be readilyapparent by the implementations disclosed herein.

FIG. 1A is a diagram depicting an example Continuous Analyte MonitoringSystem 1 having Sensor Electronics Unit 6, Continuous Analyte Sensor 8,and a plurality of Display Devices 20A-E that can be connected to SensorElectronics Unit 6. Continuous Analyte Monitoring System 1 can includeAnalyte Sensor System 4 and Display Devices 20A-E. Analyte Sensor System4 can be operatively connected to Host 2 and a plurality of DisplayDevices 20A-E according to certain aspects of the present disclosure. Insome cases, Display Devices 20A-E can run a software application, suchas a mobile application (e.g., a mobile application downloaded from anentity that created and/or owns and/or licenses the app, and/or an appstore such as from APPLE, INC. or GOOGLE INC., or other), also referredto as an app, that performs the functionality and/or has the structuredescribed throughout this disclosure.

Display device 20E alternatively or in addition to being a displaydevice, may be a medicament delivery device that can act cooperativelywith Analyte Sensor System 4 to deliver medicaments to Host 2. By way ofillustration, and without limitation, Display Device 20E can be aninsulin delivery pump, an insulin delivery pen, or other devices fordelivery medication. Analyte Sensor System 4 can include SensorElectronics Unit 6 and Continuous Analyte Sensor 8, which can beassociated with Sensor Electronics Unit 6. Sensor Electronics Unit 6 maybe in direct wireless communication with one or more of the plurality ofDisplay Devices 20A-E via wireless communications signals or wiredcommunication signals. As will be discussed in greater detail below,Display Devices 20A-E may also communicate amongst each other and/orthrough each other to Analyte Sensor System 4. Wireless communicationssignals from Analyte Sensor System 4 to Display Devices 20A-E caninclude uplink Signals 12. Wireless communications signals from DisplayDevices 20A-E to Analyte Sensor System 4 can be include downlink Signals14. Wireless communication signals can also be between two or more ofDisplay Devices 20A-E. By way of illustration, crosslink Signal 16 canbe signal communications between Display Device 20A and Display Device20C.

Sensor Electronics Unit 6 can include sensor electronics that areconfigured to process sensor information and/or send and/or receivesensor data to one or more Display Devices 20A-E. FIG. 1A illustratesDisplay Devices 20A-E, but as will be discussed in this disclosure withreference to FIG. 2A, Continuous Analyte Monitoring System 1 can haveany number of Display Devices 20A-N. Display Device 20, as usedthroughout this disclosure, represents any one of Display Devices 20A-N.In certain implementations, Sensor Electronics Unit 6 can includeelectronic circuitry associated with measuring and processing data fromContinuous Analyte Sensor 8, including prospective algorithms associatedwith processing and/or calibration of the continuous analyte sensordata. Sensor Electronics Unit 6 can be integral with (e.g.,non-releasably attached to) or releasably attachable to the ContinuousAnalyte Sensor 8 achieving a physical connection therebetween. SensorElectronics Unit 6 may include hardware, firmware, and/or software thatenable analyte level measurement. For example, and without limitation,Sensor Electronics Unit 6 can include a potentiostat, a power source forproviding power to Continuous Analyte Sensor 8, other components usefulfor signal processing and data storage, and a telemetry module fortransmitting data from itself to one or more Display Devices 20A-N.Electronics can be affixed to a printed circuit board (“PCB”), or thelike, and can take a variety of forms. For example, the electronics cantake the form of an integrated circuit (“IC”), such as anApplication-Specific Integrated Circuit (“ASIC”), a microcontroller,and/or a processor. Examples of systems and methods for processingsensor analyte data are described in more detail herein and in U.S. Pat.Nos. 7,310,544 and 6,931,327 and U.S. Patent Publication Nos.2005/0043598, 2007/0032706, 2007/0016381, 2008/0033254, 2005/0203360,2005/0154271, 2005/0192557, 2006/0222566, 2007/0203966 and 2007/0108245,all of which are incorporated herein by reference in their entirety forall purposes.

Display Devices 20A-N can be configured for displaying, alarming, and/orbasing medicament delivery on the sensor information that has beentransmitted by Sensor Electronics Unit 6 (e.g., in a data package thatis transmitted to one or more of Display Devices 20A-N based on theirrespective preferences). Each of Display Devices 20A-N can include adisplay such as a touchscreen display for displaying sensor informationto a user (e.g., Host 2 or a care taker/medical professional) and/orreceiving inputs from the user. In some implementations, Display Devices20A-N may include other types of user interfaces such as a voice userinterface instead of or in addition to a touchscreen display forcommunicating sensor information to the user of Display Devices 20A-Nand/or receiving user inputs. In some implementations, one, some, or allof Display Devices 20A-N can be configured to display or otherwisecommunicate the sensor information as it is communicated from SensorElectronics Unit 6 (e.g., in a data package that is transmitted torespective Display Devices 20A-N), without any additional prospectiveprocessing required for calibration and real-time display of the sensorinformation.

In some implementations, Display Device 20A can be a specialized medicalreceiver, specially designed for displaying certain types of displayablesensor information associated with analyte values received from SensorElectronics Unit 6 (e.g., a numerical value and a direction such astrending upward or downward). In some implementations, Display Device20C can be a handheld device, such as a mobile phone based on theAndroid or iOS operating system, a palm-top computer and the like, whereDisplay Device 20C can have a relatively larger display and beconfigured to display a graphical representation of the continuoussensor data (e.g., including current and/or historic data). Otherdisplay devices can include other hand-held devices, such as a tablet(e.g., Display Device 20D), a smart watch (e.g., Display 20B), amedicament delivery device (e.g., Display Device 20E), a blood glucosemeter, and/or a desktop or laptop computers.

As alluded to above, because the different Display Devices 20A-N canprovide different user interfaces, content of the data packages (e.g.,amount, format, and/or type of data to be displayed, alarms, and thelike) can be customized (e.g., programmed differently by themanufacturer and/or by a user) for each particular display device and/ordisplay device type. Accordingly, in some implementations, one or moreof Display Devices 20A-N can be in direct or indirect wirelesscommunication with Sensor Electronics Unit 6 to enable a plurality ofdifferent types and/or levels of display and/or functionality associatedwith the sensor information, which is described in more detail elsewhereherein.

Continuous Analyte Sensor 8 can be, for example and without limitation,a subcutaneous, transdermal (e.g., transcutaneous), or intravasculardevice. In some implementations, Continuous Analyte Sensor 8 can analyzea plurality of intermittent blood samples, although Continuous AnalyteSensor 8 can be configured to use any method of analyte-measurement,including enzymatic, chemical, physical, electrochemical,spectrophotometric, polarimetric, calorimetric, iontophoretic,radiometric, immunochemical, and the like.

Continuous Analyte Sensor 8 can use any known method, includinginvasive, minimally invasive, and non-invasive sensing techniques (e.g.,fluorescent monitoring), to provide a data stream indicative of theconcentration of a measured analyte in Host 2. In some implementations,this data stream can be typically a raw data signal, which can beconverted into a calibrated and/or filtered data stream that is used toprovide a useful value of the measured analyte to a user, such as Host 2or a caretaker (e.g., a parent, a relative, a guardian, a teacher, adoctor, a nurse, and/or any other individual that has an interest in thewell-being of Host 2). It should be understood that the devices andmethods described herein can be applied to any device capable ofdetecting a concentration of an analyte and providing an output signalthat represents the concentration of the analyte.

In some implementations, Continuous Analyte Sensor 8 can be capable ofmeasuring a concentration of glucose in Host 2, one of which isdescribed below as utilizing an implantable continuous glucose sensor.For example, and without limitation, Continuous Analyte Sensor 8 can bean implantable glucose sensor, such as described with reference to U.S.Pat. No. 6,001,067 and U.S. Patent Publication No. US-2005-0027463-A1.In another implementation, Continuous Analyte Sensor 8 can be atranscutaneous glucose sensor, such as described with reference to U.S.Patent Publication No. US-2006-0020187-A1. In still otherimplementations, Continuous Analyte Sensor 8 can be configured to beimplanted in a host vessel or extracorporeally, such as is described inU.S. Patent Publication No. US-2007-0027385-A1, co-pending U.S. PatentPublication No. US-2008-0119703-A1 filed Oct. 4, 2006, co-pending U.S.Patent Publication No. US-2008-0108942-A1 filed on Mar. 26, 2007, andco-pending U.S. Patent Application No. US-2007-0197890-A1 filed on Feb.14, 2007. In one alternative implementation, Continuous Analyte Sensor 8can comprise a transcutaneous sensor such as described in U.S. Pat. No.6,565,509 to Say et al., for example. In another alternativeimplementation, Continuous Analyte Sensor 8 can comprise a subcutaneoussensor such as described with reference to U.S. Pat. No. 6,579,690 toBonnecaze et al. or U.S. Pat. No. 6,484,046 to Say et al., for example.In another alternative implementation, Continuous Analyte Sensor 8 cancomprise a refillable subcutaneous sensor such as described withreference to U.S. Pat. No. 6,512,939 to Colvin et al., for example. Inanother alternative implementation, Continuous Analyte Sensor 8 ancomprise an intravascular sensor such as described with reference toU.S. Pat. No. 6,477,395 to Schulman et al., for example. In anotheralternative implementation, Continuous Analyte Sensor 8 can comprise anintravascular sensor such as described with reference to U.S. Pat. No.6,424,847 to Mastrototaro et al., for example. Each of theaforementioned patents and patent applications are herein incorporatedby reference.

FIG. 1B illustrates an example flow chart showing an example initiationof Sensor Electronics Unit 6 from manufacturing to use by a user. SensorElectronics Unit 6 can have a predetermined life cycle comprising theexample method 50. In Block 52, Sensor Electronics Unit 6 can bemanufactured in a factory setting. In some cases, the manufacturing caninvolve circuit fabrication, assembly, testing, calibration, etc. InBlock 54, once Sensor Electronics Unit 6 is manufactured, it can then beput in a shelf mode and/or any low power mode, which will be describedmore with reference to FIG. 6E, as well as elsewhere throughout thisdisclosure. This shelf mode and/or any low power mode can enable SensorElectronics Unit 6 to consume less power before it is used. In Block 56,as the Sensor Electronics Unit 6 is in shelf mode, it can be transportedto a user. As a non-limiting illustrative example, a Sensor ElectronicsUnit 6 can be in shelf mode as it is shipped, placed into storage,and/or before it is activated by a user. There are other instances wherea Sensor Electronics Unit 6 may be put into shelf mode and/or any lowpower mode, which will be described throughout this disclosure.

In Block 58, when it is desirable for the Sensor Electronics Unit 6 tobe activated and used, the Sensor Electronics Unit 6 can be woken out ofshelf mode and/or any low power mode. For example and withoutlimitation, in some cases, the Sensor Electronics Unit 6 canperiodically check to see if it is connected to a Continuous AnalyteSensor 8. This periodic check can involve sensing the current and/orvoltage across electrodes. In some cases, as an illustrative example andwithout limitation, the periodic check can occur at a predetermined timeintervals and/or after a predetermined number of counts, such as every5, 10, 15, or any desirable number of minutes. If there is a change incurrent and/or voltage indicative at least in part of a connection to aContinuous Analyte Sensor 8 (e.g., an increase in current and/orvoltage, and/or a change over a certain period of time and/or counts)the Sensor Electronics Unit 6 can wake up. In certain cases, apredetermined threshold can be used for the current, voltage, number ofcounts, time, etc. such that when the currents, voltages, numbers ofcounts, time, etc. exceed (or fall below when appropriate) thatpredetermined threshold, the Sensor Electronics Unit 6 wakes up. In someimplementations, if the Sensor Electronics Unit 6 has an accelerometer,waking up can occur much faster. For example, and without limitation,while in shelf mode, the Sensor Electronics Unit 6 can perform a currentcheck once every five (5) minutes or at longer intervals. If theaccelerometer detects motion, the Sensor Electronics Unit 6 can wake upand reduce the intervals at which it checks for current. The SensorElectronics Unit 6 can go back into shelf mode if the current remainsunder the wake-up threshold and no motions are detected for a certainperiod of time. Advantageously, the accelerometer can facilitate muchshorter warm-up times without shelf life being impacted. The motion canbe indicative of a user getting ready to use the Sensor Electronics Unit6.

In Block 60, after the Sensor Electronics Unit 6 wakes up, theContinuous Analyte Sensor 8 of the Sensor Electronics Unit 6 can begininitialization. The initialization can be part of a warm up period wherethe Sensor Electronics Unit 6 and/or Continuous Analyte Sensor 8 runsoftware, calibrates, runs diagnostics, etc.

In Block 62, the Sensor Electronics Unit 6 can pair with one or moreDisplay Devices 20A-N. In order to pair with display devices, the SensorElectronics Unit 6 can first advertise (e.g., broadcasting to displaydevices for connection) to pair with display devices. Advertising by theSensor Electronics Unit 6 can include using a communication protocol,such as, without limitation, BLUETOOTH® (e.g., BLUETOOTH® Low Energy(“BLE”), classic BLUETOOTH®, Dual-mode BLUETOOTH®, etc.), IBEACONS®,ZIGBEE®, Wi-Fi, induction wireless data transmission, radiotransmission, radio-frequency identification (“RFID”), near-fieldcommunication (“NFC”), and/or any other communication protocol desiredand/or mentioned in this disclosure. As used herein, any reference toBLUETOOTH® can include BLE, classic BLUETOOTH®, Dual-mode BLUETOOTH®,and/or any other BLUETOOTH® protocol. Any Display Devices 20A-Nreceiving the advertisement can send a connection request to the sensorelectronics device 6. The Sensor Electronics Unit 6 and the DisplayDevices 20A-N can then proceed with the appropriate steps to pair usingthe communication protocol used (e.g., authentication, connection,encryption/decryption, exchanging data, etc.).

In Block 64, once one or more Display Devices 20A-N and a SensorElectronics Unit 6 are paired, a user can calibrate the ContinuousAnalyte Sensor 8 and/or Sensor Electronics Unit 6. In some cases, theuser can use finger sticking to take measurements indicative of his/herblood glucose levels. He/she can enter those measurements into one ormore Display Devices 20A-N, which can transmit the data using acommunication protocol to the Sensor Electronics Unit 6, where themeasurements can be used to calibrate the Continuous Analyte Sensor 8.For example, and without limitation, the measurements can beincorporated into a calibration function which can be used by aContinuous Analyte Sensor 8 and/or Sensor Electronics Unit 6 to convertmeasurements taken by Continuous Analyte Sensor 8 or (e.g., currentand/or voltage measurements) into measurements indicative of bloodglucose levels, such as, without limitation, measurements with unitsmmol/L or mg/dL. In some cases, the calibration function can be used inone or more Display Devices 20A-N and not in the Continuous AnalyteSensor 8 and/or Sensor Electronics Unit 6. In such a case, raw data(e.g., voltages, currents, counts) can be sent to Display Devices 20A-N,where it can be converted to measurements indicative of blood glucoselevels. After calibration, the Sensor Electronics Unit 6 can go into atransmission cycle, where it can communicate with connected DisplayDevices 20A-N and/or any other desired devices.

In Block 66, the Sensor Electronics Unit 6 can connect to the one ormore Display Devices 20A-N and transmit/receive communications in atransmission cycle, where Sensor Electronics Unit 6 sends relevant data(e.g., analyte data) to the one or more Display Devices 20A-N. As anexample illustration, and without limitation, the Sensor ElectronicsUnit 6 and the Display Devices 20A-N can be connected during thetransmission cycle using the following procedures. The SensorElectronics Unit 6 can periodically advertise at predetermined timeintervals, such as every 5, 10, 15, and/or any number of minutes asdesired. The advertisement window can be anywhere from 7 seconds to 22seconds. In some cases, the duration of the advertisement window can beopen longer to allow for a plurality of Displays Devices 20A-N (e.g., areceiver and/or mobile devices) to connect and/or exchange data and/orcommands/requests. The duration of any given interval can be dependenton the type of each of Display Devices 20A-N present.

This transmission cycle can be influenced by the battery constraints ofthe Sensor Electronics Unit 6. Modifying advertising parameters such asadvertising interval or duration can directly impact the total batterylife of the Sensor Electronics Unit 6. Through testing, these parameters(e.g., advertisement intervals and durations) can be tuned to optimizethe time it takes for the different Display Devices 20A-N to connect. Insome cases, these parameters can be smartly tuned in order to adaptivelychange in operation by monitoring past connection performance in orderto set, for example, the advertisement intervals and duration. By doingso, having the Displays Devices 20A-N connect as fast as possible canreduce the total average time of advertising when a Display Device 20A-Nis nearby.

As mentioned, in some cases Continuous Analyte Monitoring System 1 cancomprise a Sensor Electronics Unit 6 operatively and/or communicativelycoupled to a Continuous Analyte Sensor 8. The Sensor Electronics Unit 6can receive data (raw and/or processed) from Continuous Analyte Sensor8. Also as mentioned, the Sensor Electronics Unit 6 can communicate toone or more Display Devices 20A-N using a communication protocol, suchas, without limitation, a radio transmission including BLUETOOTH®.Through this communication protocol, the Sensor Electronics Unit 6 cansend data to the one or more Display Devices 20A-N, including, withoutlimitation, data based at least in part on the received sensorinformation. The one or more Display Devices 20A-N can also send data,commands, and/or other communication to the Sensor Electronics Unit 6.

In some cases, where the Sensor Electronics Unit 6 and one or moreDisplay Devices 20A-N connect using radio transmission such asBLUETOOTH®, the Sensor Electronics Unit 6 can play the role of aperipheral device, which is an auxiliary device that is configured toconnect, and in some cases support, the central devices which the useruses. In this situation, the Display Devices 20A-N can play the roles ofcentral devices. In this setup, the central devices can be responsiblefor scanning for a peripheral device to connect to. By way ofillustration, using this terminology (which is sometimes used in theart) for abundance of clarity, a peripheral device (e.g., the SensorElectronics Unit 6) can advertise that it is available for a connectionand accept connection requests made by central devices (e.g., DisplayDevices 20A-N). In some implementations, the peripheral device may notserve more than a predetermined number of connections in onetransmission window (e.g. 1, 2, 3, 4, 5, 6, or more connections). Toallow for the peripheral device to request data periodically, such asevery 5, 10, 15 and/or any number of desired minutes, the centraldevices can scan, connect, exchange data, and ultimately disconnect in atimely manner. The peripheral device can enforce timeouts within theconnection to prevent central devices from staying connected longer thanexpected. The peripheral device can use a white list, as previouslydescribed, to permit specific central devices, or types of devices, toconnect. This can mean that even though it is advertising itself asconnectable, a central device may be rejected from connecting due to thewhite list feature being enabled for different central devices.

In some implementations, a Sensor Electronics Unit 6 can communicatewith one or more Display Devices 20A-N using a plurality ofcommunication channels. FIG. 1C illustrates Sensor Electronics Unit 6communicating over two different Communication Channels 106, 108 withDisplay Device 20. As previously mentioned, Display Device 20, as usedthroughout this disclosure, represents any one of Display Devices 20A-N.

Sensor Electronics Unit 6 and Display Device 20 can communicate over aplurality of communication protocols over Communication Channels 106,108. As used herein, communication protocols can include anycommunication system configured to transmit information between two ormore electronics, including, without limitation, wired and wirelesstechnologies such as BLUETOOTH®, IBEACONS®, ZIGBEE®, Wi-Fi, inductionwireless data transmission, radio frequencies, RFID, NFC, GSM, infrared,Ethernet cables, coaxial cables, Universal Serial Bus (“USB”), firewire,data lines, wire, and/or any wired and/or wireless connection known inthe art. In some cases, communication protocols can utilize radiotransmission, such as that used by BLUETOOTH®. Radio transmission isdescribed further throughout this disclosure, including with referenceto FIGS. 5A-B. In some cases, communication protocols can utilizeelectromagnetic radio waves (e.g., the electro induction between antennaloops) and/or radio frequency (“RF”) fields, such as those used by NFCor RFID. Radio transmission and RF fields are described furtherthroughout this disclosure, including with reference to FIGS. 5A-B. Andwhere particular communication protocols are discussed in reference toexamples, it should be understood that other communication protocolscould be used as well.

As an illustrative example, Communication Channel 106 can utilize RFfields, such as, without limitation, NFC or RFID. Communication Channel108 can utilize radio transmission, such BLUETOOTH®. In the case whereCommunication Channel 106 is NFC or and Communication Channel 108 isBLUETOOTH®, NFC or RFID can provide some advantages over BLUETOOTH®,including, without limitation, having little interference in crowds,ease of use, automatic pairing when in proximity, lower power usage, andothers. Similarly, BLUETOOTH® can have advantages over NFC or RFID suchas high speed of data transmission, increased range, autonomouscommunications with multiple different devices, automatically scheduledtransmissions and others.

In some implementations, as will be described in this disclosure, data,commands, statuses, and/or other communications between SensorElectronics Unit 6 and Display Device 20 can be transmitted overdifferent communication protocols, such as Communication Channels 106,108, depending on context, such as the range of the communicationprotocol or the speed of data transfer. In some cases, communicationover multiple communication protocols, together and/or sequentially, canbe used to provide additional security, usability, and/or otherdesirable advantages. Each of the multiple communication protocols usedcan have different characteristics that can be utilized differently, andfor different advantages in different uses.

FIG. 2A illustrates a block diagram of an example system where a SensorElectronics Unit 6 is communicatively coupled to a plurality of DisplayDevices 20A-N using a plurality of Communication Channels 106A-N,108A-N. As used herein, “N” in Display Devices 20A-N and CommunicationChannels 106A-N, 108A-N can be indicative at least in part of the numberof display devices that can connect to Sensor Electronics Unit 6 atonce. For example, where N is B, B can be indicative at least in partthat two display devices (e.g., Display Devices 20A, B) can connect toSensor Electronics Unit 6 and can communicate with Sensor ElectronicsUnit 6 over Communication Channels 106A-B, 108A-B. Where N is C, C canbe indicative that at least in part that three display devices (e.g.,Display Device 20A,B,C) can communication over Communication Channels106A-C, 108A-C. Similarly, N can be indicative at least in part of anynumber of display devices. In some cases, this number of display devicesthat can connect to Sensor Electronics Unit 6 can be predetermined inthe manufacturing and/or configuration of Sensor Electronics Unit 6. Forexample, two (2) or three (3) display devices can connect to SensorElectronics Unit 6 in many example configurations, however, this numberis not limited, and more can connect. In some cases, the number ofdisplay devices that can connect to Sensor Electronics Unit 6 can belimited by the communication protocol and/or the energy consumption ofthe communication protocol. For example, and without limitation, someversions of BLUETOOTH® may be limited to up to seven (7) displaydevices.

In some cases, one or more of Communication Channels 106A-N can utilizethe same communication protocols as each other. In some cases, one ormore of Communication Channels 106A-N can utilize the differentcommunication protocols from each other. Similarly, in some cases, oneor more of Communication Channels 108A-N can utilize the samecommunication protocols as each other, or one or more of CommunicationChannels 108A-N can utilize different communication protocols from eachother. Also, in some cases, any of Communication Channels 106A-N canutilize the same communication protocols as any of CommunicationChannels 108A-N. Similarly, in some cases, any of Communication Channels106A-N can utilize different communication protocols as any ofCommunication Channels 108A-N. That is, it is appreciated that any kindof permutation of different communication protocols can be used as theCommunication Channels 106A-N, 108A-N between Sensor Electronics Unit 6and Display Devices 20A-N. As a non-limiting example, CommunicationChannels 106A-N each can use a first communication protocol, such as aradio transmission like BLUETOOTH®, and Communication Channels 108A-Ncan each use a second, different communication protocol, such as an RFfield like NFC or RFID. Communication between each of Display Devices20A-N can also use any of the communication protocols described in thisdisclosure, including radio transmission (e.g., BLUETOOTH®) or RF fields(e.g., NFC or RFID).

FIG. 2B illustrates an example system where an example SensorElectronics Unit 6 is communicatively coupled to two example DisplayDevices 20A, C, and Display Device 20A and Display Device 20C areconfigured to communication with each other. Display Devices 20A,C areparticularly illustrative because in many implementations, especiallyfor CGM systems, a user may have Display Device 20A as a specializeddisplay device and one other Display Device 20C, which can be a mobiledevice. However, Display Devices 20A,C are illustrated merely asexamples, and any other display device, including any of Display Devices20A-N, can instead be used. Display Devices 20A,C can communicate witheach other through Communication Channel 259. Over Communication Channel259, Display Devices 20A,C can utilize any communication protocoldescribed in this disclosure. By way of illustrative example, andwithout limitation, Display Devices 20A,C can communicate with eachother using an RF field such as NFC or RFID. For example, using NFC orRFID, Display Devices 20A,C can transmit data (e.g., estimated bloodglucose levels, pairing information, information about a SensorElectronics Unit 6, calibration information, timing information (e.g.,time synchronizations, EGV data with time stamps, etc.), raw sensordata, system status information, detected faults, alerts, clockinginformation, device manufacturing ID, and/or any other data and/orinformation described in this disclosure), commands/requests (e.g., datarequests, synchronization requests, pairing requests), etc. to oneanother. In some cases, information about Sensor Electronics Unit 6 canbe transmitted to allow one of Display Devices 20A,C to facilitatepairing of the other of Display Devices 20A,C to Sensor Electronics Unit6. This information can be used to allow the other of Display Devices20A,C to pair with Sensor Electronics Unit 6 using another communicationprotocol, such as a communication utilizing radio transmission,including BLUETOOTH®. For example, and without limitation, pairinginformation can be sent directly between Display Devices 20A, C or via aserver (e.g., a network, cloud, etc.). By way of illustration, andwithout limitation, a user can pair Display Device 20A with SensorElectronics Unit 6. Subsequently, the pairing information (e.g., timinginformation, encryption key, authentication information, advertisingparameters, address, make/model, name, GAP, IRK, and/or any otherrelevant information for pairing) of Sensor Electronics Unit 6 can besent to Display Device 20C from Display Device 20A directly, or DisplayDevice 20A can send that pairing information to a server, which DisplayDevice 20C can then access. Accordingly, Display Device 20C can downloadthe pairing information uploaded by Display Device 20A. With the pairinginformation, Display Device 20C can then more easily pair with SensorElectronics Unit 6. In some cases, Display Device 20C can download thepairing information by signing into a mobile application (e.g., a mobileapplication downloaded from an entity that created and/or owns and/orlicenses the app, and/or an app store such as from APPLE, INC. or GOOGLEINC., or other companies). After sign in, this mobile application cancommunicate with the server and obtain the pairing information soDisplay Device 20C can connect with the Sensor Electronics Unit 6.Advantageously, allowing Display Devices 20A,C to communicate in thisway can allow pairing information to be shared quickly and efficiently,which can reduce communication traffic between Display Device 20A and/orDisplay Device 20C and Sensor Electronics Unit 6. Moreover, it can allowDisplay Devices 20A,C to update and/or receive information (e.g., viathe server) when Display Devices 20A,C are not within range of eachother and/or Sensor Electronics Unit 6. Having this ability to updateand/or receive information can be advantageous in keeping a plurality ofDisplay Devices 20A,C updated even when they are not connected to SensorElectronics Unit 6. Such transfer of pairing information between DisplayDevices 20A,C can be advantageous in allowing a healthcare practitionerto set up a system for a user. For example, and without limitation, thehealthcare practitioner could have Display Device 20C that can send overthe pairing information of a patient's Display Device 20A during setupof Display Device 20A. This can allow the healthcare practitioner tofacilitate the patient's use of Display Device 20A, especially when thepatient is a child, elderly person, handicapped, or otherwise not fullycapable of setting up Display Device 20A. As another non-limitingexample, a user may want to use Display Device 20C and uses DisplayDevice 20A to send over the pairing information.

Estimated blood glucose levels can be sent between Display Devices 20A,Cto facilitate viewing of information regarding the user of SensorElectronics Unit 6. For example, and without limitation, Display Device20A can be a display device of a user. Display Device 20C can be adisplay device belonging to a medical practitioner. Transmission, usingan RF field, such as NFC or RFID, of data from Display Device 20A toDisplay Device 20C can comprise past data that can allow the healthpractitioner to analyze the behavior of the patient's blood glucoselevel and provide therapy. Advantageously, NFC or RFID can allow asecure way of transferring such data without the need for pairing. Also,since the doctor may ultimately retrieve data from a plurality ofdisplay devices, or have a plurality of display devices to which he/shecan connect using a radio transmission such as BLUETOOTH®, the abilityto use NFC or RFID can allow the doctors to save battery in his/herdisplay device (e.g., from not advertising and/or having tore-authenticate) and may allow the practitioner to not mistakenlyconnect to another device in the vicinity. In other uses, the data sentvia NFC or RFID can be used for backfill purposes in order to allow oneof Display Devices 20A-B to send past data to the other. In some cases,present data can also be sent via NFC or RFID between Display Devices20A-B. A person having ordinary skill in the art should appreciate thatother communication protocols can be used as well to transfer data, suchas Wi-Fi or any other communication protocol described in thisdisclosure.

In some implementations, a communication protocol (e.g., NFC, RFID,Wi-Fi, BLUETOOTH® and/or any other communication protocol described inthis disclosure or known in the art) can be used to synchronize alertson Display Devices 20A,C. For example, and without limitation, Wi-Fi canbe used so that when a user acknowledges an alert or communication onone of Display Devices 20A,C, such acknowledgment is viewable on theother of Display Devices 20A,C. Advantageously, this can allow aplurality of users and devices to coordinate regarding therapy of a userof a Sensor Electronics Unit 6, and/or prevent excessive alerts andcommunications for multiple users and/or a single user using multipledevices.

FIG. 3 illustrates a functional block diagram of example SensorElectronics Unit 6. Sensor Electronics Unit 6 can include Controller301, Memory 302, Power Supply 303, and/or Operative Units 304, each ofwhich can be operatively and/or communicatively coupled to each otherand each other's components and/or subcomponents. Controller 301 cancontrol the various operations performed by Sensor Electronics Unit 6.In some implementations, Sensor Electronics Unit 6 can be configured toperform the example processes, methods, and/or systems, and/orsubstantially similarly processes, methods, and/or systems describedwith reference to Sensor Electronics Units 6 throughout this disclosure.

Controller 301 can be operatively and/or communicatively coupled toMemory 302, which can include, without limitation, volatile,non-volatile, read-only memory (“ROM”), and/or random access memory(“RAM”), and can provide instructions and data to Controller 301. Aportion of Memory 302 can also include non-volatile random access memory(“NVRAM”). Controller 301 can perform logical and/or arithmeticoperations based on program instructions stored within Memory 302.Controller 301 can include one or more processors (e.g.,microprocessors) and other peripherals. The instructions in Memory 302can be executable to implement the methods described herein. Forexample, Memory 302 can be a non-transitory, computer-readable storagemedium having a plurality of instructions stored thereon, theinstructions being executable by a processing apparatus (e.g.,Controller 301) to operate Sensor Electronics Unit 6. Operative Units304 can be coupled to Controller 301 to perform the various operationsdescribed in this disclosure. One or more, or none, of the units inOperative Units 304 can be included in some implementations. Throughoutthis disclosure, reference will be made to various controllers and/orprocessors. In some implementations, a single controller (e.g.,Controller 301) can serve as the various controllers and/or processorsdescribed. In other implementations, different controllers and/orprocessors can be used. Controller 301 can send and/or receive signals,such as power signals, control signals, sensor signals, interrogatorysignals, status signals, data signals, electrical signals and/or anyother desirable signals, including discrete and analog signals.Controller 301 can coordinate and/or manage Operative Units 304, and/orset timings (e.g., synchronously or asynchronously), turn on/off,control power budgets, receive/send network instructions and/or updates,update firmware, send interrogatory signals, receive and/or sendstatuses, and/or perform any operations for running features of SensorElectronics Unit 6.

Operative Units 304 can include various units that perform functions forSensor Electronics Unit 6. For example, and without limitation, suchunits of Operative Units 304 can include Communicators 305, Data Storage306, Data Manager 307, Signal Processor 308, and/or Operating Systems310.

In some implementations, Communicators 305 can communicatively coupleSensor Electronics Unit 6, and/or any components therein (e.g.,Operative Units 304), to one or more display devices (e.g., DisplayDevice 20A-N and/or any other display device described in thisdisclosure). Communicators 305 can be configured to send/receivecommunications over wired and/or wireless connections, such as any wiredand/or wireless connection described in this disclosure. For example,and without limitation, Communicators 305 can utilize a communicationprotocol configured to send and/or receive data over communicationchannels. For example, and without limitation, such communicationprotocols can include BLUETOOTH®, IBEACON®, ZIGBEE®, Wi-Fi, inductionwireless data transmission, radio frequencies, radio transmission, RFfields, RFID, NFC, GSM, infrared, Ethernet cables, coaxial cables, USB,firewire, data lines, wire, and/or any wired and/or wireless connectionknown in the art. For example, and without limitation, Communicators 305can include an antenna, inductor, signal line, ground line, and/or anyother electronics used for sending/receiving data. In the case of NFC,RFID, and/or substantially similar technologies, Communicators 305 caninclude readers, writers, and/or tags.

Communicators 305 can be configured to send and/or receive statuses,commands, and/or other data/information. For example, and withoutlimitation, Communicators 305 can transmit statuses, commands, and/ordata/information from Data Storage 306, Data Manager 307, SignalProcessor 308, Operating Systems 310, Operative Units 304, Controller301, Memory 302, Power Supply 303, and/or any other component and/orsubcomponent of Sensor Electronics Unit 6.

Data Storage 306 can be configured to temporarily and/or permanentlystore (e.g., record) data. Data Storage 306 can include storage devicesthat can store data using different mediums, such as, withoutlimitation, electrical (e.g., semiconductors, floating-gate transistors,hard disks, flash memory, RAM, ROM, enterprise storage, cloud,distributive storage devices, etc.), optical storage (e.g.,photographic, microform, holographic, optical disk, magneto-opticaldrives, 3D optical data storage, holographic data storage), chemicals(e.g., organics, proteins, synapses, receptors, chemical concentrations,etc.), thermodynamics (e.g., phase change materials, heat storagedevices, etc.), photochemicals (e.g., films, etc.), mechanical (e.g.,switches), magnetic storage (e.g., magnetic tape, wire, etc.), etc. DataStorage 306 can also store any data and/or information based at least inpart on data from any component of Sensor Electronics Unit 6, includingController 301, Power Supply 303, Memory 302, and/or units in OperativeUnits 304.

Data Manager 307 can be configured to analyze and/or manage data in DataStorage 309, Memory 302, and/or any component of Sensor Electronics Unit6 (e.g., Controller 301, Power Supply 303, and/or units in OperativeUnits 304). Operations that Data Manager 307 can use on such datainclude, but are not limited to, compression, decompression, sorting,categorizing, directing, optimizing, defragging, deleting, secureerasing, securing, manipulating, identifying, copying, pasting, writeprotecting (e.g., temporary write protection or permanent writeprotection), backing up, authenticating, etc. Data Manager 307 can alsoperform error monitoring, error correction, and/or data validation,including identifying and/or fixing transmission-related errors, dataformatting, device-related error codes, invalid data, duplicate datapoints, and/or other processes on the data.

Signal Processor 308 can be configured to process any data of SensorElectronics Unit 6, including, as a non-limiting example, data stored inData Storage 306 and/or managed by Data Manager 307. Signal Processor308 can perform any analysis of data presented in this disclosure, aswell as other analyses and/or processes.

Power Supply 303 can include one or more batteries, including, withoutlimitation, lithium, lithium ion, nickel-cadmium, nickel-metal hydride,nickel-hydrogen, carbon-zinc, silver-oxide, zinc-carbon, zinc-air,mercury oxide, alkaline, or any other type of battery known in the art.Certain batteries can be rechargeable, such as wirelessly (e.g., by aresonant circuit and/or a resonant tank circuit) and/or by plugging intoan external power source. Power Supply 303 can also be any supplier ofenergy, including wall sockets and electronic devices that convertsolar, wind, water, nuclear, hydrogen, gasoline, natural gas, fossilfuels, mechanical energy, steam, and/or any power source intoelectricity. Power Supply 303 can have sensors (not illustrated) thatmonitor the amount of power available. For example, and withoutlimitation, where a battery is used, the sensors can measure the amountof battery life remaining. A sensor can detect and/or approximate thelife of the battery of a Sensor Electronics Unit 6. In someimplementations, the sensor for battery life can actively measure thecharge, capacitance, chemical composition, or potential of a batteryunit. In some cases, the sensor can be a timer that approximates thelife of the Sensor Electronics Unit 6, such as 1, 2, 3, 4, 5, 6 or moremonths. The approximate time or percentage of battery life used orremaining may be displayed in one or more display devices and/or thesensor electronics unit 6. In some cases, the sensor can keep track ofbattery usage (e.g., as counts, power budgets, voltage consumption,current consumption, approximated leakage, etc.) and sum the amount ofbattery usage over time. A running total can be kept and compared to thetotal battery budget (e.g., as counts, power budgets, voltage budget,current budgets, etc.) to approximate the remaining and/or used life ofthe battery.

Operating System 310 can be configured to manage Memory 302, Controller301, Power Supply 303, units in Operative Units 304, and/or anysoftware, hardware and/or features of Sensor Electronics Unit 6. Forexample, and without limitation, Operating System 310 can include devicedrivers to manage hardware resources for Sensor Electronics Unit 6.

Any of the aforementioned components of Sensor Electronics Unit 6 can beinstantiated in software and/or hardware. For example, a unit can bepiece(s) of hardware and/or can be a unit/module of code run on acomputer. Hardware can include processors, circuit logic, etc.

FIG. 4A illustrates a functional block diagram of example Display Device20. As previously mentioned, Display Device 20, as used throughout thisdisclosure, represents any one of Display Devices 20A-N. In someimplementations, Display Device 20 can be configured to perform theexample processes, methods, and/or systems, and/or substantiallysimilarly processes, methods, and/or systems described with reference todisplay devices throughout this disclosure.

Controller 401 can be operatively and/or communicatively coupled toMemory 402, which can include, without limitation, volatile,non-volatile, ROM, and/or RAM, and can provide instructions and data toController 401. A portion of Memory 402 can also include NVRAM.Controller 401 can perform logical and arithmetic operations based onprogram instructions stored within Memory 402. Controller 401 caninclude one or more processors (e.g., microprocessors) and otherperipherals. The instructions in Memory 402 can be executable toimplement the methods described herein. For example, Memory 402 can be anon-transitory, computer-readable storage medium having a plurality ofinstructions stored thereon, the instructions being executable by aprocessing apparatus (e.g., Controller 401) to operate Display Device20. Operative Units 404 can be coupled to Controller 401 to perform thevarious operations described in this disclosure. One or more, or none,of the units in Operative Units 404 can be included in someimplementations. Throughout this disclosure, reference will be made tovarious controllers and/or processors. In some implementations, a singlecontroller (e.g., Controller 401) can serve as the various controllersand/or processors described. In other implementations, differentcontrollers and/or processors can be used. Controller 401 can sendand/or receive signals, such as power signals, control signals, sensorsignals, interrogatory signals, status signals, data signals, electricalsignals and/or any other desirable signals, including discrete andanalog signals. Controller 401 can coordinate and/or manage OperativeUnits 404, and/or set timings (e.g., synchronously or asynchronously),turn on/off, control power budgets, receive/send network instructionsand/or updates, update firmware, send interrogatory signals, receiveand/or send statuses, and/or perform any operations for running featuresof Display Device 20.

Operative Units 404 can include various units that perform functions forDisplay Device 20. For example, and without limitation, such units ofOperative Units 404 can include Communicators 405, Data Storage 406,Data Manager 407, Signal Processor 408, User Interface 409 and/orOperating Systems 410.

In some implementations, Communicators 405 can communicatively coupleDisplay Device 20, and/or any components therein (e.g., Operative Units404), to one or more sensor electronics units (e.g., Sensor ElectronicsUnit 6). Communicators 405 can be configured to send/receivecommunications over wired and/or wireless connections, such as any wiredand/or wireless connection described in this disclosure. For example,and without limitation, Communicators 405 can utilize a communicationprotocol configured to send and/or receive data over communicationchannels. For example, and without limitation, such communicationprotocols can include BLUETOOTH®, IBEACON®, ZIGBEE®, Wi-Fi, inductionwireless data transmission, radio transmission, RF fields, radiofrequencies, RFID, NFC, GSM, infrared, Ethernet cables, coaxial cables,USB, firewire, data lines, wire, and/or any wired and/or wirelessconnection known in the art. For example, and without limitation,Communicators 405 can include an antenna, inductor, signal line, groundline, and/or any other electronics used for sending/receiving data. Inthe case of NFC, RFID, and similar technologies, Communicators 405 caninclude readers, writers, and/or tags.

Communicators 405 can be configured to send and/or receive statuses,commands, and/or other data/information. For example, and withoutlimitation, Communicators 405 can transmit statuses, commands, and/ordata/information from Data Storage 406, Data Manager 407, SignalProcessor 408, Operating Systems 410, Operative Units 404, Controller401, Memory 402, Power Supply 403, and/or any other component and/orsubcomponent of Sensor Electronics Unit 20.

Data Storage 406 can be configured to temporarily and/or permanentlystore (e.g., record) data. Data Storage 406 can include storage devicesthat can store data using different mediums, such as, withoutlimitation, electrical (e.g., semiconductors, floating-gate transistors,hard disks, flash memory, RAM, ROM, enterprise storage, cloud,distributive storage devices, etc.), optical storage (e.g.,photographic, microform, holographic, optical disk, magneto-opticaldrives, 3D optical data storage, holographic data storage), chemicals(e.g., organics, proteins, synapses, receptors, chemical concentrations,etc.), thermodynamics (e.g., phase change materials, heat storagedevices, etc.), photochemicals (e.g., films, etc.), mechanical (e.g.,switches), magnetic storage (e.g., magnetic tape, wire, etc.), etc. DataStorage 406 can also store any data and/or information based at least inpart on data from any component of Display Device 20, includingController 401, Power Supply 403, Memory 402, and/or units in OperativeUnits 404.

Data Manager 407 can be configured to analyze and/or manage data in DataStorage 406, Memory 402, and/or any component of Display Device 20(e.g., Controller 401, Power Supply 403, and/or units in Operative Units404). Operations that Data Manager 407 can use on such data include, butare not limited to, compression, decompression, sorting, categorizing,directing, optimizing, defragging, deleting, secure erasing, securing,manipulating, identifying, copying, pasting, write protecting (e.g.,temporary write protection or permanent write protection), backing up,authenticating, etc. Data Manager 407 can also perform error monitoring,error correction, and/or data validation, including identifying and/orfixing transmission-related errors, data formatting, device-relatederror codes, invalid data, duplicate data points, and/or other processeson the data.

Signal Processor 408 can be configured to process any data of DisplayDevice 20, including, as a non-limiting example, data stored in DataStorage 406 and/or managed by Data Manager 407. Signal Processor 408 canperform any analysis of data presented in this disclosure, as well asother analyses and/or processes.

User Interface 409 can be configured for a user to communicate withDisplay Device 20. For example, and without limitation, User Interfaces409 can include touch panels, buttons, keypads/keyboards, ports (e.g.,USB, DVI, Display Port, E-Sata, Firewire, PS/2, Serial, VGA, SCSI,audioport, HDMI, PCMCIA ports, memory card ports (e.g., SD and miniSD),and/or ports for computer-readable medium), mouse, rollerballs,consoles, vibrators, audio transducers, and/or any interface for a userto input and/or receive data and/or commands, whether coupled wirelesslyor through wires (including, without limitation, any of the wireless orwired connections described in this disclosure). User Interface 409 caninclude a display, such as, without limitation, LCDs, LED displays, LEDLCD displays, IPSs, cathode ray tubes, plasma displays, HD panels, 4Kdisplays, retina displays, organic LED displays, touchscreens, surfaces,canvases, and/or any displays, televisions, monitors, panels, and/ordevices known in the art for visual presentation.

Power Supply 403 can include one or more batteries, including, withoutlimitation, lithium, lithium ion, nickel-cadmium, nickel-metal hydride,nickel-hydrogen, carbon-zinc, silver-oxide, zinc-carbon, zinc-air,mercury oxide, alkaline, or any other type of battery known in the art.Certain batteries can be rechargeable, such as wirelessly (e.g., by aresonant circuit and/or a resonant tank circuit) and/or by plugging intoan external power source. Power Supply 403 can also be any supplier ofenergy, including wall sockets and electronic devices that convertsolar, wind, water, nuclear, hydrogen, gasoline, natural gas, fossilfuels, mechanical energy, steam, and/or any power source intoelectricity. Power Supply 403 can have sensors (not illustrated) thatmonitor the amount of power available. For example, and withoutlimitation, where a battery is used, the sensors can measure the amountof battery life remaining. A sensor can detect and/or approximate thelife of the battery of a Display Device 20. In some implementations, thesensor for battery life can actively measure the charge, capacitance,chemical composition, or potential of a battery unit. In some cases, thesensor can be a timer that approximates the life of Display Device 20,such as 1, 2, 3, 4, 5, 6 or more months. The sensor can then display theapproximate time or percentage of battery life used or remaining. Insome cases, the sensor can keep track of battery usage (e.g., as counts,power budgets, voltage consumption, current consumption, approximatedleakage, etc.) and sum the amount of battery usage over time. A runningtotal can be kept and compared to the total battery budget (e.g., ascounts, power budgets, voltage budget, current budgets, etc.) toapproximate the remaining and/or used life of the battery.

Operating System 410 can be configured to manage Memory 402, Controller401, Power Supply 403, units in Operative Units 404, and/or anysoftware, hardware and/or features of Display Device 20. For example,and without limitation, Operating System 410 can include device driversto manage hardware resources for Display Device 20.

Any of the aforementioned components of Display Device 20 can beinstantiated in software and/or hardware. For example, a unit can bepiece(s) of hardware and/or can be a unit/module of code run on acomputer. Hardware can include processors, circuit logic, etc.

FIG. 4B is an example advertising/connection sequence between an exampleSensor Electronics Unit 6 and Display Device 20. The various tasksperformed in connection with the advertising/connection illustrated inFIG. 4B may be performed by a processor/controller executinginstructions embodied in a non-transitory computer-readable medium. Forexample, the tasks performed in connection with the procedure may beperformed by hardware, software, firmware, or any combination thereofincorporated into one or more of computing devices, such as SensorElectronics Unit 6 and/or Display Device 20. It should be appreciatedthat the procedure may include any number of additional or alternativetasks. The tasks shown in FIG. 4B may not be performed in theillustrated order, and the procedure may be incorporated into a morecomprehensive procedure or process having additional functionality notdescribed in detail herein.

In the example described below, the analyte values can be glucose valuesbased on one or more measurements from Continuous Analyte Sensor 8.However, it should be understood that the analyte values can be anyother analyte value described herein. The wireless data communicationbetween Sensor Electronics Unit 6 and Display Device 20 may happenperiodically, at times separated by an update interval denoted“T_(interval)” that may correspond to a time duration between twoconsecutive wireless communication sessions between a Communicators 305of the Sensor Electronics Unit 6 (e.g., Communicators 305) and theCommunicators 405 of Display Device 20 (e.g., Communicators 405).Alternatively, the update interval may be a period of obtaining andsending a recently measured glucose value. Transmitting advertisementsignals, establishing a data connection (e.g., a communication channel),authentication, and requesting and sending data may occur duringwireless communication sessions each lasting an active time or period(also referred to as timings) denoted “T_(Active)” within an updateinterval T_(interval). In between two consecutive wireless communicationsessions, the communication units can go into an inactive or sleep modefor an inactive period denoted as “T_(Inactive) ^(”) to conserve batterylife and/or reduce peak voltage requirements, for example.

FIG. 4B illustrates an example where two such wireless communicationsessions, namely, a first wireless Communication Session 410 and asecond wireless Communication Session 420. Each wireless CommunicationSession 410, 420 starts with Sensor Electronics Unit 6 establishing adata connection with Display Device 20. To establish a data connectionwith Display Device 20, the Communicators Unit 305 of Sensor ElectronicsUnit 6 can transmit a series of Advertisement Signals 412 during thefirst wireless Communication Session 420. Each advertisement signal maybe considered an invitation for Communicators 405 of Display Device 20to establish a data connection with Communicators 305 of SensorElectronics Unit 6. In some implementations, advertisement signals 412may be embodied as advertising beacons, as will be discussed in greaterdetail below. It should be noted that in some implementations,Advertisement Signals 412 themselves can have advertising parameters sothat directed or targeted advertising can be performed to a specificDisplay Device 20 or type of device.

In some cases, Sensor Electronics Unit 6 can engage in an initial systemsetup when Sensor Electronics Unit 44 is powered on because SensorElectronics Unit 6 can just be turning on for the first time and/or maynot be currently paired with Display Device 20. Typically, a user ofDisplay Device 20 can identify a new and/or never-been used SensorElectronics Unit 6 that can be paired with Display Device 20 by enteringidentification information (e.g., a serial number) associated with thenew/unpaired Sensor Electronics Unit 6 via an application (e.g., adownloadable Java Script via the Internet and/or a mobile applicationdownloaded from an entity that created and/or owns and/or licenses theapp, and/or an app store such as from APPLE, INC. or GOOGLE INC., orother companies), running on Display Device 20 using User Interface 409.During the first wireless Communication Session 410, an authenticationprocedure can be performed as part of Data Connection Process 414, whichcan be a first data connection process. In some embodiments, informationmay be obtained from a passive tag or communicator 305 incorporated intothe Sensor Electronics Unit 6, for instance using an NFC reader inDisplay Device 20 to read the passive NFC tag. For instance and withoutlimitation, the passive NFC tag may store data such as calibration ormanufacturing information including identification informationassociated with Continuous Analyte Sensor 8 or Sensor Electronics Unit6. In some cases, the Display Device 20 is configured to readinformation from the passive tag (e.g., via communicator 405) aftercompletion of the authentication procedure. In some cases, at least aportion of the information stored on the passive tag is encrypted. Insome embodiments, the tag may be placed on a base of the sensorelectronics module 6. In such embodiments, the stored information (e.g.,information related to the sensor or the sensor electronics module) inthe passive tag may be initially read by the display device 20.Following that, the display device may transmit the captured informationto the sensor electronics module 6 or other display devices via awireless protocol (e.g., NFC or BLE).

To establish a data connection with the Sensor Electronics Unit 6,Display Device 20 can listen continuously or periodically until anadvertisement signal transmitted by the Communicators 305 of SensorElectronics Unit 6 is received. Once the Communicators 305 of SensorElectronics Unit 6 begin transmitting Advertisement Signals 412, it maytake one, two, or more advertisement signals for Display Device 20 toreceive at least one of the advertisement signals and respond to atleast one of the advertisement signals. In some cases, extendedadvertising can consume energy and/or battery life of Sensor ElectronicsUnit 6. In some implementations, the Communicators 305 of SensorElectronics Unit 6 can stop sending additional advertisement signalsonce Display Device 20 receives an advertisement signal and responds tothat advertisement signal, for example, via an acknowledgement. In otherimplementations, Communicators 305 of Sensor Electronics Unit 6 cancontinue to send additional advertisement signals even after receiving aresponse from Display Device 20 so that another display device (e.g.,one or more of Display Devices 20A-N), can receive and/or respond to atleast one of the additional advertisement signals. After anadvertisement signal is successfully received by Display Device 20,Display Device 20 and Sensor Electronics Unit 6 can engage in DataConnection Process 414.

During Data Connection Process 414, Display Device 20 can request achallenge value from Sensor Electronics Unit 6 and Sensor ElectronicsUnit 6 can send the challenge value to Display Device 20 in response.Upon receiving the challenge value, Display Device 20 can calculate ahash value based on the challenge value and the identificationinformation associated with Sensor Electronics Unit 6 and/orCommunicators 305 of Sensor Electronics Unit 6 and sends the hash valueto Communicators 305 of Sensor Electronics Unit 6. Communicators 305 ofSensor Electronics Unit 6 can receive the hash value from Display Device20, decode the identification information from the hash value, andverify that the received identification information matchesidentification information associated with Sensor Electronics Unit 6and/or the Communicators 305 of Sensor Electronics Unit 6 previouslystored in the memory of Sensor Electronics Unit 6 (e.g., Memory 302),such as during manufacturing of Sensor Electronics Unit 6. Uponverification, Communicators 305 of Sensor Electronics Unit 6 can send asignal confirming a successful authentication to Display Device 20. Onceauthenticated, Sensor Electronics Unit 6 and Display Device 20 canexchange information to determine how data will be exchanged (e.g., aspecific frequency, time slot assignment, encryption, etc.).

After completion of the Data Connection Process 414, Sensor ElectronicsUnit 6 and now-connected Display Device 20 can engage in a first DataCommunication 416 during which Display Device 20 can request and/orreceive desired information (e.g., analyte measurement data, controlinformation, identification information, and/or instructions) fromSensor Electronics Unit 6. When the first Data Communication 416 iscompleted, the data connection can be terminated (e.g., by closing theestablished communication channel) and the Communicators 305 and/orController 301 of Sensor Electronics Unit 6 can be deactivated bycausing the Communicators 305 and/or Controller 301 to enter a sleep orinactive mode (e.g., low power mode or shelf mode). In someimplementations, the Communicators 305 of Sensor Electronics Unit 6 canbe completely or substantially completely powered down during a sleepmode (e.g., low power or shelf mode). In some implementations, theCommunicators 305 of Sensor Electronics Unit 6 can be in a low powermode using only a small fraction (e.g., 1-50%) of the normalcurrent/power. As will be discussed further below with reference toFIGS. 6C-D, as well as elsewhere throughout this disclosure, theCommunicators 305 of Sensor Electronics Unit 6 may be woken up, forexample, by a communication protocol using an RF field, such as NFC orRFID, which places an on-demand request from a Display Device 20.

The active period T_(Active) corresponding to a duration of eachwireless communication session may be a small fraction of the updateinterval T_(interval) corresponding to a period between two consecutivewireless communication sessions. For example, T_(interval) may bebetween about 200 and 20 seconds and T_(Active) may be between 20 and 40seconds. As such, the Communicators 305 of the Sensor Electronics Unit 6may be powered fully for only 10 percent (e.g., 30 seconds) of a fiveminute T_(interval). This may significantly reduce power consumption andpeak voltage demand. In some cases, that Communicators 305 may notcompletely power down, but enter a low-power mode when not transmitting.After an inactive time or period T_(Inactive), a second wirelessCommunication Session 420 can start when the Communicators 305 of SensorElectronics Unit 6 powers up again, begins transmitting a second seriesof Advertisement Signals 422, engages in a second data ConnectionProcess 424 and a second data Communication Process 426 with theCommunicators 405 of Display Device 20 as shown in FIG. 4B. Unlike thefirst data Connection Process 414, however, the second data ConnectionProcess 424 need not involve an authentication procedure because theSensor Electronics Unit 6 and the Display Device 20 have beensuccessfully paired or bonded during the first wireless CommunicationSession 410 as described above. This process may continue, with new dataconnections and communications being completed at the pre-determinedintervals. During all or part of each inactive period T_(Inactive)during which the Communicators 305 of Sensor Electronics Unit 6 is in asleep mode, the Controller 401 of Sensor Electronics Unit 6 can takemeasurement(s) of one or more analyte values using the analyte sensorand sensor measurement circuitry. For example, and without limitation,the Controller 401 or Sensor Electronics Unit 6 may take multipleanalyte value measurements and average them to generate a singleaveraged analyte value to be transmitted in a next wirelesscommunication session.

Continuously re-establishing a new communication channel to allow forpartially or wholly powering down the Communicators 305 of SensorElectronics Unit 6 during each update interval T_(interval) can providesignificant power savings. For example, the cycle of re-establishing newcommunication channels and powering down the Communicators 305 can allowthe Sensor Electronics Unit 6 to operate for, e.g., 1 month, 3 months, 6months, 1 year, etc., without battery replacement. It should be notedthat in some implementations, battery replacement can be a function ofthe actual expiration of battery power or some predetermined level ofremaining battery power. Furthermore, rather than globally transmittingglucose data points during the update interval T_(interval),establishing specific data connections (e.g., communication channels)with only desired display devices, e.g., Display Device 20 and/or anyDisplay Devices 20A-N, can prevent unauthorized use and interception ofglucose measurement values. In some implementations, only a subset ofmultiple display devices (e.g., Display Device 20A-N) can be configuredto receive different data such as glucose measurement values and/oralarm conditions. For example, and without limitation, in addition to adisplay device identifier(s), a white list may be populated with a datatype identifier indicative of a type of data to be sent to thatparticular display device(s) populating the white list. For example, andwithout limitation, the particular display device(s) can have a datatype identifier indicative of the display device receiving glucosemeasurement data and/or alarm conditions, such as low blood glucoselevels. In other implementations, Sensor Electronics Unit 6 can bepre-programmed with preference or profile information, which can beaccessed to determine what type(s) of data are to be sent to whatdisplay device(s). Thus, prior to the exchange of sensor information,Sensor Electronics Unit 6 can access the white list (or bonding list insome implementations) and/or preference/profile information to determinewhat type(s) of data should be sent to a display device. In still otherimplementations, initial communications between Sensor Electronics Unit6 and a Display Device 20, the Display Device 20 can transmit typeinformation (e.g., the type of information that the display deviceshould receive) to Sensor Electronics Unit 6. This has a benefit ofpreventing all of Display Devices 20A-N communicating with SensorElectronics Unit 6 from issuing alarms, thereby confusing and/orfrustrating the user. In addition, by establishing a secure two-waycommunication channel, requests for specific glucose measurement valuesor communication of calibration or configuration information may betransmitted on an as-needed/requested basis between Sensor ElectronicsUnit 6 and Display Device 20.

Also, in some implementations, the Communicators 305 of SensorElectronics Unit 6 may not be activated for data communication everyupdate interval T_(interval). Instead, Communicators 305 of SensorElectronics Unit 6 may be activated every second, third, or fourthupdate interval T_(interval), for example, so that communication betweenthe Sensor Electronics Unit 6 with Display Device 20 occurs lessfrequently than every update interval T_(interval). Doing so can furtherreduce power consumption. Activation could also depend on the sensorinformation. For example, Communicators 305 of Sensor Electronics Unit 6need only be activated if data meets certain thresholds, such as acurrent rate of change, current high value, current low value, absolutedifference from a previously exchanged value, percentage difference froma previously exchanged value, and the like. In some implementations,instead of skipping certain fixed update intervals, the length of eachinterval can be made to vary based on the sensor information or othercriteria. For example, and without limitation, if the sensor informationindicates a low glucose value and/or a hypoglycemic reaction isdetected, the update interval value can be shortened from a normal,longer update interval value so that more frequent readings are takenand/or transmitted.

In some implementations, one or more of the update intervalT_(interval), the active period T_(Active), and a frequencyF_(Activation) by which the transceiver is activated (e.g., everysecond, third or fourth update interval) may be variable. In certainimplementations, the above-identified parameters can be userconfigurable (e.g., by inputting a value for the variable using userinterface of Display Device 20) and/or automatically varied by theSensor Electronics Unit 6 or Display Device 20 based on one or morecriteria. The criteria can include: (i) a monitored battery power (e.g.,using Power Supply 303) of Sensor Electronics Unit 6, (ii) a currentlymeasured, previously measured and/or predicted glucose concentrationsmeeting or exceeding a predetermined threshold, (iii) a glucoseconcentration trend of the host based on currently measured, previouslymeasured and/or predicted glucose concentrations, (iv) a rate of changeof glucose concentration of the host based currently measured,previously measured and/or predicted glucose concentrations meeting orexceeding a predetermined threshold, (v) whether the host is determinedto be in or near hyperglycemia based on currently measured, previouslymeasured and/or predicted glucose concentrations, (vi) whether the hostis determined to be in or near hypoglycemia based on currently measured,previously measured and/or predicted glucose concentrations, (vii) userinputted activity of the host (e.g., exercising or sleeping), (viii)time since a sensor session has started (e.g., when a new sensor isused), (ix) one or more errors detected by Sensor Electronics Unit 6and/or Display Device 20 and/or (x) type of Display Device 20 (e.g.,where Display Device 20 can be connected or populating the white list orbonding list).

T_(interval), T_(Active), F_(Activation) and/or other configurationitems described herein may form part of a communication protocol profilethat may be stored on any device that implements the fundamentalcommunication protocol to allow for a customized use of the protocol forcommunicating analyte measurement values in the Sensor Electronics Unit6 and one or more of Display Devices 20.

In some implementations, communication protocols can have differentranges and/or different authentication protocols. FIG. 5A illustratesexample ranges of example communication protocols of an example SensorElectronics Unit 6 having two communication protocols, where eachcommunication protocol has a different range. As described earlier,communication protocols can include any communication protocol known inthe art, including those described in this disclosure. For example, andwithout limitation, Range 506 can be indicative at least in part of therange of RF fields, such as, without limitation, NFC or RFID. Byexample, where NFC has Range 506, Range 506 can be in the order ofcentimeters, such as ten centimeters or less. Because of the shortrange, in many cases, NFC can have simple and/or automatic connectionbetween devices using the NFC communication protocol. NFC-enableddevices can include devices that work with NFC card emulation, NFCreader/writer, and/or NFC peer-to-peer. NFC can transfer data with ratesin the range of 106 to 424 kbits/s, or any other speed as thecommunication protocol's standards are updated from time-to-time. Insome cases, NFC communicates at 13.56 MHz. In some cases, the initiatingdevice of a transmission using NFC can generate an RF field that canpower the receiving device. In many cases, NFC is desirable due to itssecurity and simplicity. However, NFC communication protocols can havelimited range. NFC is sometimes considered to be included by someskilled in the art as a subset and/or outgrowth of the RFID family oftechnologies. Generally, RFID technologies can have variable ranges,including those having ranges up to 2000 feet. An RFID system can beActive Reader Passive Tag (“ARPT”) with an active reader device thattransmits interrogator signals and also receives authentication repliesform passive tags. In some cases, an RFID system can be Active ReaderActive Tag (“ARAT”) where an active tag is awoken with an interrogatorsignal from an active reader. RFID can work in a range of frequencybands, such as, without limitation, 120-150 kHz, 13.56 MHz, 433 MHz,865-868 MHz, 902-928 MHz, 2450-5800 MHz, 3.1-10 GHz. As used herein,communication protocols using RF fields can include other RF fieldsbesides NFC or RFID, including other RF fields operating in thefrequency ranges of 13.56 MHz, 120-150 kHz, 13.56 MHz, 433 MHz, 865-868MHz, 902-928 MHz, 2450-5800 MHz, 3.1-10 GHz. NFC or RFID are merely usedas illustrative examples.

Range 508 can be indicative at least in part of a second communicationprotocol. For example, and without limitation, the second communicationprotocol can utilize radio transmission, such as BLUETOOTH®. By way ofillustrative example, and without limitation, in the case where thesecond communication protocol is BLUETOOTH®, Range 508 can be overapproximately thirty feet. In some cases, BLUETOOTH® can have a usermanually set up connections between devices, such as a procedure whereone device detects the other device, and the devices are paired and/orauthenticated. BLUETOOTH® may transmit in the ISM band from 2.4 to 2.485GHz, or any frequency as the BLUETOOTH® standard is updated fromtime-to-time. BLUETOOTH® version can have relatively high speeds of datatransfer, such as up to 800 kbits/s. In many cases, BLUETOOTH® isfavored for its speed and range. However, there can be issues ofconnectivity, energy consumption, excessive handshaking, droppedpackets, security, etc. As used herein, radio transmission can includeother radio transmission protocols besides BLUETOOTH®, including otherradio transmissions operating in the frequency range of 2.4 to 2.485GHz. BLUETOOTH® is merely used as an illustrative example.

Similarly, FIG. 5B illustrates example ranges of example communicationprotocols of an example Display Device 20, where each communicationprotocol has a different range. Ranges 556, 558 can be substantiallysimilar to Ranges 506, 508, respectively. As mentioned, variouscommunication protocols can be used, such as those using RF fields(e.g., NFC or RFID) or radio transmission (e.g., BLUETOOTH®).

FIG. 5C illustrates an example functional block diagram illustratingcertain functional units of Display Device 20. These functional unitscan be instantiated in software and/or hardware. For example, a unit canbe piece(s) of hardware and/or can be a unit/module of code run on acomputer. Hardware can include processors, circuit logic, etc.

Wake Unit 654 can implement a waking action where the user can useDisplay Device 20 to wake up a Sensor Electronics Unit 6 from, forexample and without limitation, a low power mode and/or shelf mode(e.g., as described with reference to FIGS. 4B, 6C-D, as well aselsewhere throughout this disclosure). In some cases, waking up SensorElectronics Unit 6 can include sending a wake up command to SensorElectronics Unit 6.

Pair Unit 655 can be used to pair the Display Device 20 with SensorElectronics Unit 6, which can be configured for communication via radiotransmission (e.g., BLUETOOTH®) and/or any other communication protocoldescribed in this disclosure. In some cases, where Display Device 20 andthe Sensor Electronics Unit 6 have not been paired with thatcommunication protocol before, Pair Unit 655 can include one or more ofa command to pair, initial setup information, timing information,advertising parameters, device information, frequency, sequence,encryption/decryption information, and/or other parameters. Thisfunctionality and more will be discussed later with reference to FIG. 8,as whereas elsewhere throughout this disclosure. In cases where theDisplay Device 20 has paired with the Sensor Electronics Unit 6, PairUnit 655 can include adding (if not already) the Display Device 20 tothe white/bonding list, advertising to the Display Device 20,connecting, authentication, exchanging data, etc.

Calibrate Unit 656 can be used to calibrate the Sensor Electronics Unit6. For example, and without limitation, a user can measure his/her bloodglucose levels through finger pricking. He/she can enter that data(e.g., through a User Interface 409 into a field (not illustrated)) onDisplay Device 20 and send information based at least in part on thatdata to a Sensor Electronics Unit 6 over an RF field communicationprotocol such as NFC or RFID. Advantageously, calibration can be timesensitive where a user can desire to adjust and/or add new calibrationparameters soon so that he/she has the correct readings. Advantageously,calibration using an RF field such as NFC or RFID can be accomplished ondemand and without the need of following pairing procedures.

Retrieve Data Unit 657 can be used to request to retrieve data from theSensor Electronics Unit 6. In some cases, retrieving data can comprise acommand to send data over another communication protocol other than thecommunication protocol used to request the data. The command cancomprise a request for data along with what data to send (e.g., the last1, 2, 3, 4, 5, 6, 7, 8, 9, 10 or more data points), types of data (e.g.,sensor data or electronics unit logs), timeframes of data (e.g.,including time stamps), etc. By way of illustrative example, the secondcommunication protocol used by Display Device 20 to request the sendingof data from Sensor Electronics Unit 6 can utilize an RF field, such asNFC or RFID. The second communication protocol used to transfer data canbe radio transmission, such as BLUETOOTH®. Advantageously, sending thedata over the radio transmission instead of the RF field can allow forfaster transfer rates and transfer over longer distances. For example,where it is desirable to retrieve the data on Display Device 20, a usercan use that Display Device 20 to initiate data transfer from the SensorElectronics Unit 6 to the Display Device 20 using RF fields such as NFCor RFID, and then walk further away while the data transfers over radiotransmission such as BLUETOOTH®. If the data were transferred over NFC,it might take longer and/or the user would have to stay close to theSensor Electronics Unit 6. Having the flexibility to move around,including further away, during data transfer may be advantageous forhealthcare practitioners as they treat the user and other patients.

In some cases, the command to send data can be a command that requeststhe data to be sent over NFC. Such may be desirable when security isimportant (e.g., the user wants data to only be sent to close devices),the sensor electronics has little or no battery life, and/or anysituation desired by a user. In some implementations, the determinationof when to use NFC for data transfer can be determined by Display Device20 or Sensor Electronics Unit 6, such as using NFC when only a smallamount of data is transferred.

Set White/Bonding List Unit 658 can be used to set a white/bonding list.In some communication protocols, such as radio transmissioncommunication protocols, can have one or more white lists and/or bondinglists that can be used by a Sensor Electronics Unit 6 to manageconnected devices. The role of the white list can include a list ofdevices and/or their pairing information (e.g., timing information,encryption key, authentication information, advertising parameters,address, make/model, name, Generic Access Profile (“GAP”), IdentityResolving Key (“IRK”), etc.) for which Sensor Electronics Unit 6 can bepaired. In some cases, the white list can be stored in memory of theSensor Electronics Unit 6 and updated. In some implementations, therecan be a predetermined number of slots in the white list, such as 1, 2,3, 4, 5, or more slots. The display devices listed in the white list canconnect for communication with Sensor Electronics Unit 6. For example,and without limitation, a Display Device 20 can be added to the whitelist, after which, the pairing information from the Display Device 20can be pulled by the Sensor Electronics Unit 6 from the bonding list.Once the Display Device 20 is connected, the white list can be updatedto only allow that specific Display Device 20, and other display deviceson its white list, to connect.

A bonding list can include a predetermined number of slots, such as 1,2, 3, 4, 5, or more slots. The bonding list can be stored in memory, andin some cases, it can be maintained by an application on the SensorElectronics Unit 6 or on a display device (e.g., Display Device 20). Thebonding list can contain the authentication and/or pairing information(e.g., timing information, encryption key, authentication information,advertising parameters, address, make/model, name, GAP, IRK, etc.) for apredetermined number of display devices. The display devices whoseinformation is on the bonding list may or may not be on the white list.

In some cases, the Display Device 20 may not be on the white list.Placing that Display Device 20 may be desirable, and convenient, to theuser because he/she is presently using that Display Device 20. Forexample, and without limitation, if a user is using a receiver, but thenwants to use a smart phone and leave the receiver elsewhere, the usermay desire to quickly add the smart phone to the white list. As will bedescribed later in this disclosure with reference to FIG. 9A, in somecases, Set White/Bonding List Unit 658 can include sending a command toadd the Display Device 20 to the white list of Sensor Electronics Unit 6along with the pairing information of Display Device 20. Thisinformation can be added to any open slot in the white list. In someimplementations, as will be discussed later in this disclosure withreference to FIG. 9C, Set White/Bonding List Unit 658 can includeremoving Display Device 20 from the white list so the Sensor ElectronicsUnit 6 does not communicate with it, and Sensor Electronics Unit 6 andDisplay Device 20 do not inadvertently connect. For example, a user canhave a plurality of display devices (including Display Device 20) andmay not want to get the same alerts on all of them.

In some cases, as will be discussed later in this disclosure withreference to FIG. 9D, Sensor Electronics Unit 6 can communicate witheach Display Device 20 on its white list in a particular order, such asin sequential order (e.g., starting with the first slot and going to thenth slot). In such a case, some slots may allow Display Device 20 toconnect and receive information relatively faster than other slots inthe same white list. For example, and without limitation, some slots onthe white list only allow the device to connect less frequently thanwhen on other slots, such as only every 20 minutes instead of every 5minutes. Also, different slots in the white list can have differentparameters associated with it that can impact, for example and withoutlimitation, the reliability of the connection. Accordingly, along with acommand to add the Display Device 20 to the white list of a sensorelectronics device, and any other associated data desirable (e.g.,pairing information), Set White/Bonding List Unit 658 can include arequest to add the Display Device 20 to a particular slot in the whitelist. For example, and without limitation, the Display Device 20 canrequest to be added to the first slot. Advantageously, this can allowthe Display Device 20 to have preferable reliability and connection,and/or faster reception of data in some situations.

In some cases, adding a Display Device 20 to the white list can haverepercussions to other display devices in the white list. Where therequested slot in the white list is empty, the Display Device 20'sinformation (e.g., pairing information) can be simply added to thatempty slot. However, there can be other situations. For example, andwithout limitation, where the Display Device 20 requests to be in a slotthat is already filled, Set White/Bonding List Unit 658 can includeinstructions on what should be done with that previously occupyingdisplay device. In some cases, as will be discussed later in thisdisclosure with reference to FIG. 9D, Set White/Bonding List Unit 658can include a request to remove the display device occupying the desiredslot of the new Display Device 20. In this way, the previously occupyingdisplay device can be removed from the white list (and in some cases,the bonding list too). In other cases, as will be discussed later inthis disclosure with reference to FIG. 9E, Set White/Bonding List Unit658 can include a request that shifts the display devices in laterdesignated slots down and removes the display device in the last slot.For example, and without limitation, in the case where there are threeslots in the white list, numbered 1 to 3, each of which is filled, SetWhite/Bonding List Unit 658 can include a request to add the pairingdisplay device to slot 1. A temporary white list can be made in memoryholding the previous contents of the white list. The information fromprevious slot 1 can then be put into slot 2, and the information fromprevious slot 2 can be put in slot 3. The information from previous slot3 can then not be added to the white list.

In some cases, Set White/Bonding List Unit 658 can also designate whichdisplay device should be removed from the white list. In the previousexample, Set White/Bonding List Unit 658 can include a request to addthe present display device to slot 1, remove the display devicepreviously in slot 2 and shift the devices according. In that situation,the new display device would be added to slot 1, the display devicepreviously in slot 1 would be added to slot 2, and the display device inslot 3 would stay put.

Set White/Bonding List Unit 658 can also include any number ofreorderings of the white list. In some cases, the white list can bereordered without adding any new devices. Advantageously, this can allowthe user to dynamically adjust his/her preferences. In these situations,Set White/Bonding List Unit 658 can include one or more requestsinstructing Sensor Electronics Unit 6 how to reorder the white listand/or where each device should go. In some cases, where Display Device20 has information regarding the white list of Sensor Electronics Unit 6beforehand (e.g., a previous exchange of the white list and/or structureof the white list from Sensor Electronics 6 to Display Device 20), thiscan include a white list map (e.g., a bit map and/or pointers indicatinghow to reorder the white list) transmitted to the Sensor ElectronicsUnit 6, letting the Sensor Electronics Unit 6 know where to send thecontents of each slot to another slot. The white list map can includepointers or addresses indicative at least in part of which slots thepresently listed display devices on the white list should go. Forexample, each entry in the white list map (e.g., a vector or matrix) cancorrespond to a slot in the white list. Each entry in that white listmap can include at least the address of the slot to which the presententry in the white list should move in the updated white list. In otherimplementations, Set White/Bonding List Unit 658 can include an entirelynew white list that will be used by the Sensor Electronics Unit 6 toreplace its previous white list.

As a separate action, or included in Set White/Bonding List Unit 658,the bonding list can be set. Setting the bonding list can include acommand to add or remove an item from the bonding list. Typically, theorder of the bonding list does not have implications for a user, but auser could change the order of the bonding list in a similar way asdescribed above with respect to the white list, including commands toadd and/or remove particular display devices from particular slots(e.g., identified by the display device and/or the slot number) of thebonding list, and/or reorder the bonding list. The bonding list caninclude more slots (e.g., store more devices) than the white list.

Mode of Operation Unit 659 can include setting the mode of operation.Mode of Operation Unit 659 can include a request for the SensorElectronics Unit 6 to go into shelf mode, low power mode, normaloperation, active, sleep, transmitting, idle, battery management (e.g.,to be energy efficient to reduce energy consumption such as by the useof communication protocols using RF fields, such as NFC or RFID, insteadof radio transmission such as BLUETOOTH®) and/or any mode and/or statusdesired.

Clone Unit 649 can include cloning Sensor Electronics Unit 6. Cloningcan include receiving and/or sending from Sensor Electronics Unit 6 oneor more parameters to configure a second sensor electronics unit. By wayof illustrative example, in some cases, a user may want to fully cloneSensor Electronics Unit 6 by transferring the Sensor Electronics Unit6's data and/or configurations (e.g., pairing information, calibrationdata, timings, white lists, bonding lists, etc.) to another, secondsensor electronics unit. As another illustrative example, only a subsetof the data and/or configurations of Sensor Electronics Unit 6 may betransferred. Such can be desirable when a user only wants to clonecertain aspects of the Sensor Electronics Unit 6. In some cases, pairinginformation may not be transferred between the Sensor Electronics Unit 6and the second sensor electronics unit because that information may bedevice specific and change between the units. In any of these cases,Clone Unit 649 can use a communication protocol to transfer the one ormore parameters of Sensor Electronics Unit 6 to second sensorelectronics unit.

By way of illustrative example, in some cases Sensor Electronics Unit 6and Display Device 20 may normally transfer data utilizing a firstcommunication protocol such as a radio transmission (e.g., BLUETOOTH®).In the case where a second communication protocol utilizing an RF field,such as NFC or RFID, is used on the Sensor Electronics Unit 6, CloneUnit 649 can use the second communication protocol to transfer the dataand/or configurations from Sensor Electronics Unit 6 onto Display Device20. Display Device 20 can store the data and/or configurations inmemory. In some cases, this transfer can occur while Sensor ElectronicsUnit 6 still has low battery life and/or after the battery of the SensorElectronics Unit 6 has died and the second communication protocol, suchas NFC, is also used to power the transfer. In some cases, before thebattery of the Sensor Electronics Unit 6 dies, Sensor Electronics Unit 6can upload the data and/or configurations of the Sensor Electronics Unit6 to an NFC tag that can facilitate passive transfer. In someimplementations, the second communication protocol could be used toinitiate the cloning, but the first communication protocol could be usedto actually transfer the data from one display device to another. By wayof illustrative example, the first communication protocol could be aradio transmission, such as BLUETOOTH®. Display Device 20 could initiatethe cloning of Sensor Electronics Unit 6 via the second communicationprotocol, which can utilize an RF field, such as NFC or RFID. SensorElectronics Unit 6 could then transfer its data and/or configurationsvia the first communication protocol to either a second sensorelectronics unit or Display Device 20. Where the data and/orconfigurations are transferred to Display Device 20, Display Device 20could subsequently transfer the data and/or configurations to the secondsensor electronics unit via a communication protocol, such as the firstor second communication protocols, or any other communication protocoldescribed in this disclosure. Subsequently, Display Device 20 could sendthe data and/or configurations to the second sensor electronics unit. Insome cases, this second sensor electronics unit can use the data and/orconfigurations to set itself up substantially similarly to SensorElectronics Unit 6 (e.g., with substantially similar pairings,configurations, calibrations, etc.).

FIG. 6A illustrates an example interface 620 where a user can selectfunctionality corresponding to the functional units illustrated in FIG.5C from Display Device 20. Interface 620 can be part of a mobileapplication (e.g., a mobile application downloaded from an entity thatcreated and/or owns and/or licenses the app, and/or an app store such asfrom APPLE, INC. or GOOGLE INC., or other companies) that performs thefunctionality and/or has the structure described throughout thisdisclosure, including with reference to FIG. 5C. Interface 620 cancomprise visual, audio, and/or tactile elements to interact with a userusing a Display Device 20. Interface 620 can be instantiated on UserInterface 409 (illustrated in FIG. 4A). A user may use Interface 620 inorder to access the various functionalities of Display Device 20.

In some cases, Interface 620 can have a plurality of panels that displayinformation and/or allow for user interaction. For example, and withoutlimitation, Panel 610 can include a field that shows information for asensor electronics unit (e.g., Sensor Electronics Unit 6). In somecases, by selecting the field, the user can select a sensor electronicsunit with which to use sensor functionality. The sensor electronics unitcan be identified by serial number, alias, name, code, and/or anyidentifier desired. In some implementations, the identifier can beentered manually and/or selected from a list of available (e.g.,previously entered, detected, and/or paired) sensor electronics units.Panel 611 can describe a status of the sensor electronics unitidentified in Panel 610. As some non-limiting examples, statuses caninclude one or more of: shelf mode, low power mode, normal operation,active, sleep, transmitting, idle, low battery, and/or any statusdescription. These statuses can be retrieved and displayed by Interface620 through a server (e.g., network, cloud, etc.) to which the sensorelectronics unit sends such statuses, through other communicationprotocols (e.g., radio transmission or any of the communicationprotocols described in this disclosure), and/or through previoustransmissions (e.g., via radio transmission, RF fields, and/or any othercommunication protocol described in this disclosure) that include statusinformation from sensor electronics units. Panel 612 can describe thepairing status of Display Device 20 to the sensor electronics unitdisplayed in Panel 610. As a non-limiting example, a status of unpairedcan indicate that the sensor electronics unit is not paired with theDisplay Device 20 over a communication protocol (e.g., radiotransmission, such as BLUETOOTH®, and/or any other communicationprotocol described in this disclosure). Other examples can includepaired (e.g., the sensor electronics unit is paired with the DisplayDevice 20 over a communication protocol described in this disclosure),advertising, on white list, on bonding list, and/or any other pairingstatus.

Panel 613 can include user-selectable fields on Interface 620, which,when selected, can cause Display Device 20 to initiate correspondingactions. Panel 613 can include actions that a user can take with respectto the sensor electronics unit displayed in Panel 610. These actionsinclude: Action 614, which can be a wake action implementingfunctionality corresponding at least in part to Wake Unit 654; Action615, which can be a pair action implementing functionality correspondingat least in part to Pair Unit 655; Action 616, which can be a calibrateaction implementing functionality corresponding at least in part toCalibrate Unit 656; Action 617, which can be a retrieve data actionimplementing functionality corresponding at least in part to RetrieveData Unit 657; Action 618, which can be a set white/bonding list actionimplementing functionality corresponding at least in part to SetWhite/Bonding List Unit 658; Action 619, which can be a mode ofoperation action implementing functionality corresponding at least inpart to Mode of Operation Unit 659; and Action 609, which can be a cloneaction implementing functionality corresponding at least in part toClone Unit 649.

A user can add those Actions 614, 615, 616, 617, 618, 619, 609 to aQueue 630 (illustrated in FIG. 6B), which can comprise a list of theactions stored in memory. The actions on the queue can then be used totransmit the appropriate commands, data/information, etc. in order toperform those actions. These actions can be added to Queue 630 byselecting them through Interface 620 (e.g., by touching, clicking,pushing, etc. options on a touch screen or inputted using a keyboardmouse and/or any other apparatus). A person having ordinary skill in theart should appreciate that other actions can also be included in Actions613 than those previously listed. When the user desires to transmit oneor more selected actions from Panel 613, the user can select Button 634,which can then open up Interface 640 for transmission. FIG. 6Billustrates one such interface.

FIG. 6B illustrates an example Interface 640 for performing actions inan Action Queue 630 over NFC. Action Queue 630 can comprise actionsselected from Action 613 (e.g., one or more of Actions 614, 615, 616,617, 618, 619, 609) and/or other actions. In this illustrative example,instructions are transmitted from Display Device 20 to SensorElectronics Unit 6 via NFC, however, other communication protocols canbe used, including radio transmission, RF fields, and/or any othercommunication protocol described in this disclosure. Graphic 632 canillustrate instructions to the user and tell the user to hold theDisplay Device 20 near Sensor Electronics Unit 6. In some cases, theseinstructions can tell the user to tap Display Device 20 to the SensorElectronics Unit 6 and/or hold the Display Device 20 near SensorElectronics Unit. When the Display Device 20 is placed within range ofSensor Electronics Device 6, Sensor Electronics Unit 6 can then performthe items in Action Queue 630. In some cases, Display Device 20 may alsodisplay a prompt, for example, to indicate that Display Device 20 is nowconnected via NFC.

A. Waking Up and Putting into Low Power Mode

In some implementations, Sensor Electronics Unit 6 can be placed in alow power mode, such as shelf mode, after manufacturing to preservebattery life. This placement can be done in the factory for shipment(e.g., as described with reference to FIG. 1B) and/or it can be done bya user if he/she wants to preserve battery in Sensor Electronics Unit 6.Once a user decides to start using Sensor Electronics Unit 6, SensorElectronics Unit 6 can be placed in its normal operational mode. Wakingup Sensor Electronics Unit 6 can be difficult because, in some cases,Sensor Electronics Unit 6 may not have a user interface and/or may notbe actively transmitting in order to connect to a display device (e.g.,Display Device 20) that can initiate a command to wake up.

As previously discussed, in some cases, Sensor Electronics Unit 6 canuse the activation of Continuous Analyte Sensor 8 that iscommunicatively and/or operatively coupled to Sensor Electronics Unit 6to wake up Sensor Electronics Unit 6 from the low power mode. SensorElectronics Unit 6 can be attachable to Continuous Analyte Sensor 8 withelectrodes that allow current (or voltage) to flow between the SensorElectronics Unit 6 and electrode. When Sensor Electronics Unit 6 detectsa current (or voltage) indicative of attachment to Continuous AnalyteSensor 8, Sensor Electronics Unit 6 can wake up from the low power mode.However, this way of waking up the Sensor Electronics Unit 6 can haveshortcomings in some situations. For example, and without limitation, auser can unintentionally wake up Sensor Electronics Unit 6 by touchinghis/her fingers across the electrodes and/or otherwise causing a changein current across the electrodes of Sensor Electronics Unit 6. In somecases, Sensor Electronics Unit 6 also may not sense the current betweenthe electrodes all the time. Rather, it may only do so periodically,such as every 5, 10, 15, or more minutes. In such cases, a user may haveto wait a significant amount of time before Sensor Electronics Unit 6detects the current across its electrodes and wakes up from the lowpower mode. This can result in a poor user experience.

In some cases, Sensor Electronics Unit 6 in low power mode can draw itsoperating power from the RF field associated with Display Device 20using an electromagnetic radio wave for communication. For example, andwithout limitation, a communication protocol such as NFC or RFID can beused by Display Device 20 to create an RF field that can allow a DisplayDevice 20 to communicate with Sensor Electronics Unit 6 in low powermode. Advantageously, this communication protocol (e.g., NFC or RFID)can be used by Display Device 20 to wake up Sensor Electronics Unit 6from that low power mode. The following descriptions of waking up SensorElectronics Unit 6 can be part of Action 614 utilizing Wake Unit 654. Insome implementations, Action 614 can be part of an Action Queue 630where a plurality of actions (e.g., actions in Actions 613) can beperformed.

FIG. 6C illustrates an example timing diagram where an RF field is usedto wake a Sensor Electronics Unit 6 from a low power mode. The exampletiming diagrams are timing diagrams of Sensor Electronics Unit 6. SensorElectronics Unit 6 can first be in low power mode (e.g., a shelf modeand/or any other low power mode) in Period 602, where the powerconsumption is at a lower state compared to at least one other powermode (e.g., the regular mode of operation). As discussed throughout thisdisclosure (e.g., with reference to FIGS. 1B, 5C), the low power modecan be used during shipment and/or in latent periods of SensorElectronics Unit 6 use. Transmission 604 can be made using acommunication protocol utilizing an RF field, such as NFC or RFID whenthe Sensor Electronics Unit 6 is in low power mode. Transmission 604 canbe sent to Sensor Electronics Unit 6 using a Display Device 20. In someimplementations, Transmission 604 can include a wake action, such asAction 614, and/or Action 614 can also include Transmission 604.Transmission 604 can include command(s), data, status(s), and/or anyother desired transmissions. The wake action can also include and/or beperformed in combination with other actions, such as any actions ofActions 613. For example, and without limitation, the command caninclude instructions requesting Sensor Electronics Unit 6 to wake up(e.g., Action 614) and/or go into a mode for normal operations (e.g.,Action 659), such as a mode of operations that allows for the receptionof measurements indicative of glucose measurements of the user and/ortransmission of data between Sensor Electronics Unit 6 and DisplayDevice 20. In some cases, Sensor Electronics Unit 6 can advertise toDisplay Device 20 in the mode for normal operation. This advertising caninitiate right after or substantially right after the Sensor ElectronicsUnit 6 awakens from the low power mode.

In some implementations, other commands can tell Sensor Electronics Unit6 to perform tasks, such as read data and/or current/voltage from aContinuous Analyte Sensor 8 and/or send the Display Device 20 data,statuses, commands, etc. Commands can also include commands relating tochanging mode of operation, calibrate measurement circuitry, turn on/offsensor circuits, adjust defined parameters or presets, etc. Thesecommands can also include any commands described with respect to Actions613. In some cases, Transmission 604 can include energy (e.g., energytransmitted for powering via NFC) that can be used to power from DisplayDevice 20 delivered to the Sensor Electronics Unit 6 in order to powerthe reception of the command and/or any steps desired to perform thecommand. For example, and without limitation, Transmission 604 caninclude energy from the Display Device 20 sent to Sensor ElectronicsUnit 6 (e.g., via NFC) so that the Sensor Electronics Unit 6 can receivea wake-up command and increase its power usage. In some cases, thereceived power by Sensor Electronics Unit 6 can allow Sensor ElectronicsUnit 6 to go from a low power mode to a normal power mode. Once it is ina normal power mode, it can then power its own activities. In somecases, the energy received by Sensor Electronics Unit 6 can power thewhole transition (e.g., all the actions/steps taken by SensorElectronics Unit 6) from the low power mode to a higher power mode. Insome cases, the energy received by the Sensor Electronics Unit 6 doesnot power the whole transition to a normal power mode, but cansufficiently power Sensor Electronics Unit 6 to receive the command tochange to the higher power mode from the low power mode.

Data from the Display Device 20 sent to the Sensor Electronics Unit 6 inTransmission 604 can include data about the Display Device 20 (e.g.,serial number, authentication, security information, make/model, etc.).In some cases, this data (alone or in combination with sent commands,statuses, etc.) can facilitate pairing between Sensor Electronics Unit 6and Display Device 20 using other communication protocols. Statuses caninclude the status of the display device, and/or any informationrelating to the functionality of the display device (e.g., ready,standby, errors in operation, etc.). During, after, or both during andafter Transmission 604, the Sensor Electronics Unit 6 can go into normaloperation in Period 606. Period 606 can occur after Time Delay 608 fromTransmission 604. Time Delay 608 can be a predetermined delay (e.g., 5,4, 3, 2, 1, or less seconds).

Where NFC or RFID is used, Transmission 604 can be sent using atap-to-start initiation. In particular, where NFC is used, NFC can haveranges that are in the order of a few centimeters (e.g., ten centimetersor less), where a user can bring Display Device 20 close to and/or touchSensor Electronics Unit 6 to send Transmission 604. Such physicalinteraction can be advantageous by giving the user a physical initiationthat can be intuitive. As described throughout this disclosure,tap-to-start initiation can be desirable in a variety of instances. Byway of illustration, and without limitation, tap-to-start initiation canbe used to wake up Sensor Electronics Unit 6 from a low power mode. Itcan also be used generally to change the power mode of SensorElectronics Unit 6 when desirable (e.g., to shelf, mode, normaloperation, high power mode, etc.). In some cases, NFC can be used totransmit commands, data, calibration information, etc. between DisplayDevices 20 and Sensor Electronics Unit 6. Desirably, using NFC generallyor in a tap-to-start initiation can be advantageous to allow a user tochange the settings of Sensor Electronics Unit 6 without having to gothrough multiple steps for pairing (e.g., as with BLUETOOTH®) and/orauthentication. Such use of NFC can also allow reliable data and commandtransmission, and can also be performed on-demand without having to waiton transmission timings of other communication protocols such asBLUETOOTH®.

In some implementations, normal operation in Period 606 can includeutilizing the communication of protocol of Transmission 604. In someimplementations, normal operation in Period 606 can include using asecond communication protocol, such as a communication protocol thatutilizes radio transmission. In some implementations, this secondcommunication protocol may not be the same communication protocol as thefirst communication protocol. By way of illustrative example, thissecond communication protocol can include BLUETOOTH®. In some examples,after transmitting data via the second communication protocol, theSensor Electronics Unit 6 can return to the low power mode.

FIG. 6D illustrates an example flow chart illustrating the processdescribed in FIG. 6C. In some cases, a user of a Display Device 20 maydesire to use Method 620 when he/she desires to pair his/her DisplayDevice 20 to Sensor Electronics Unit 6 substantially on demand. Forexample, and without limitation, some white lists may only let DisplayDevice 20 connect at predetermined intervals, such as every 20 minutes.Instead of waiting for that timing, a user may desire to connect DisplayDevice 20 to Sensor Electronics Unit 6 substantially right away. By wayof illustration, a user may want to add a Display Device 20 to a whitelist instantly during an emergency where there are no other displaydevices available for use. Sensor Electronics Unit 6 can be sensinganalyte measurements of the user, or of someone else (e.g., someoneunder the care of a user). Accordingly the user may use Method 620 topair Display Device 20 to Sensor Electronics Unit 6 on demand tofacilitate assistance during the emergency. As another illustrativeexample, a health practitioner may want to pair Display Device 20 to apatient's Sensor Electronics Unit 6 right away as the healthpractitioner makes rounds. Because the health practitioner may not havetime to wait for the predetermined time interval of the white list, thehealth practitioner may appropriately use Method 620 to connectinstantly with the sensor electronics unit 6 of the user. As anotherillustrative example, a user may just find it inconvenient to wait thepredetermined time interval to connect the Sensor Electronics Unit 6 toa Display Device 20. Accordingly, such a user may desire to use Method620 to connect the Display Device 20 to the Sensor Electronics Unit 6substantially on demand

In Block 622, Sensor Electronics Unit 6 can operate in a low power mode.In Block 624, Sensor Electronics Unit 6 can receive a signal using afirst communication protocol. By way of illustrative example, the secondcommunication protocol can utilize an RF field, such as NFC or RFID bySensor Electronics Unit 6 and/or Display Device 20. This transmissioncan comprise commands, such as, without limitation, commands for pairingof a first communication protocol, changing mode of operation, calibratemeasurement circuitry, turn on/off sensor circuits, adjust definedparameters or presets, etc. The transmission can also include anyaction, such as, without limitation, Actions 613. By way ofillustration, and without limitation, this transmission can include aplurality of actions queued by a user using the Display Device 20. Insome cases, these actions can include one or more of: a mode ofoperation action (e.g., Action 619), a pairing action (e.g., Action615), and/or a set white/bonding list action (e.g., Action 618).Advantageously, a mode of operation action can allow Sensor ElectronicsUnit 6 to switch from low power mode to a different mode of operation,such as a normal mode of operation. A pairing action can allow theDisplay Device 20 to communicate with Sensor Electronics Unit 6 usingthe second communication protocol to pair to the Sensor Electronics Unit6 using a first communication protocol. For example, and withoutlimitation, a second communication protocol using an RF field, such asNFC or RFID, can be used to pair a Sensor Electronics Unit 6 with aDisplay Device 20 for communications using first communication protocol,such as one using radio transmission (e.g., BLUETOOTH®), by exchangingpairing information for that first communication protocol. As describedin this disclosure, a set white list action can be used to change theorder of the white list of Sensor Electronics Unit 6 for the firstcommunication protocol as desired. In some cases, this action caninclude instructions in how to reorder the white list, pointers forchanging the white list, a copy of a new white list, and/or any otherway of setting the white list described in this disclosure (e.g., asdescribed previously with reference to FIGS. 5C, 6A). Any other actiondescribed in this disclosure can be also be used. Advantageously, thiscan allow a user flexibility and convenience in setting up connections.In some implementations, Display Device 20 can autonomously determineactions to queue, such as based at least in part on patterns of userutilization (e.g., based on the uses of one or more of Actions 614, 615,616, 617, 618, 619, 609 at particular times of day, and/or particularsituations, so Display Device 20 learns to initiate those same ofActions 614, 615, 616, 617, 618, 619, 609 at those same times of dayand/or situations) and/or on needs of the Display Device 20 (e.g.,retrieving missing data).

Next, in Block 626, Sensor Electronics Unit 6 can change from the lowpower mode to the desired operation mode. By way of illustrativeexample, various operation modes can be used, such as, withoutlimitation, a normal operation mode, calibration mode, blind mode (e.g.,a mode where all or some data is not displayed on a Display Device 20),and/or any desirable mode. In some cases, in Block 626, the desiredoperation mode can be a normal operation mode.

In Block 628, the Sensor Electronics Unit 6 can then communicate using afirst communication protocol, including, without limitation, a radiotransmission such as BLUETOOTH® and/or any other communication protocoldescribed in this disclosure. As the Sensor Electronics Unit 6communicates using this first communication protocol, it can do sowithout further user interaction because it already receivedinformation, such as pairing information, by the second communicationprotocol.

In some implementations, instead of waking up a Sensor Electronics Unit6 from a lower power mode, such as shelf mode, a user may desire to puta Sensor Electronics Unit 6 in another operating mode into a low powermode. For example, and without limitation, a user may only want tomonitor glucose once a week or every month. Because some SensorElectronics Unit 6 may have predetermined (or limited) battery lives,putting the Sensor Electronics Unit 6 into low power mode can allowSensor Electronics Unit 6 to be used for more days.

FIG. 6E illustrates an example timing diagram of Sensor Electronics Unit6 that is put into a low power mode. In Period 652, Sensor ElectronicsUnit 6 can have normal operation, or any operation using morepower/energy than a low power mode. In normal operation, SensorElectronics Unit 6 can communicate using one or more communicationprotocols, such as any communication protocol mentioned in thisdisclosure including radio transmission such as BLUETOOTH®. In someimplementations, Transmission 654 can put Sensor Electronics Unit 6 intoa low power mode during Period 656 using a command, such as a commandtelling Sensor Electronics Unit 6 to go into a low power mode and/or alow power initiation command. Period 656 can occur after Time Delay 658from Transmission 654. Time Delay 658 can be a predetermined delay(e.g., 5, 4, 3, 2, 1, or less seconds). Transmission 654 can be madeusing any communication protocol described in this disclosure. By way ofillustrative example, Transmission 654 can be made using an RF field forcommunication, such as NFC or RFID, or using radio transmission, such asBLUETOOTH®. Where NFC is used, since NFC can have ranges that are in theorder of a few centimeters (e.g., ten centimeters or less), a user canbring a Display Device 20 close to and/or touch Sensor Electronics Unit6 to send Transmission 654. Such physical interaction can beadvantageous by giving the user a physical initiation that can beintuitive. Using radio transmission such as BLUETOOTH® can beadvantageous because the Display Device 20 may be further away fromSensor Electronics Unit 6 and/or may already be communicating over radiotransmission such as BLUETOOTH® to Sensor Electronics Unit 6.

In some implementations, the low power mode can be a shelf mode, orother power modes that use less power. For example, and withoutlimitation, as mentioned with reference to FIGS. 1B, 6A, the low powermode can be a mode that turns off one or more of a transmission circuit(e.g., a BLUETOOTH® radio), measurement circuitry, sensory circuitry,processors, etc. It can also reduce the frequency of refreshes,advertisements, resolution of measurements, and/or any other periodicactivities of a Sensor Electronics Unit 6. Sensor Electronics Unit 6 canlater be woken up in a process substantially similar to the processdescribed with respect to FIGS. 6C-D.

As was mentioned in this disclosure with reference to FIGS. 6A-B, a wakeaction (e.g., Action 614 and/or other waking action described in thisdisclosure) can be performed in combination with other actions, such asone or more of Actions 613. These actions can be performed in a queue,such as Action Queue 630. For example, and without limitation, waking upa Sensor Electronics Unit 6 can be combined with any one or more ofActions 614, 615, 616, 617, 618, 619, 609.

B. Out-of-Sync Communication

In some cases, communications sent by Sensor Electronics Unit 6 canfollow certain communication patterns, such as, without limitation, thecommunication patterns described with reference to FIGS. 6C, 6E.However, in some cases, a user may desire to send/receive communicationsthat do not follow the timing of that communication pattern. By way ofexample, and without limitation, a retrieve data action, such as Action617, can be used by a display Device 20 to retrieve data from SensorElectronics Unit 6 out of the communication pattern. As was mentioned inthis disclosure, a retrieving data action (e.g., Action 617 and/or otherwaking action described in this disclosure) can be performed incombination with other actions, such as one or more of Actions 613.These actions can be performed in a queue, such as Action Queue 630.

FIG. 7A illustrates an example timing diagram of an example firstcommunication protocol for Sensor Electronics Unit 6. Measurement Line704 illustrates that Sensor Electronics Unit 6 can receive measurementssubstantially constantly. Measurement Line 704 can represent analogand/or digital measurements. In the case of a digital measurement, thecontinuous line of Measurement Line 704 can represent a recurringreception of discrete digital data measurements.

Communication Line 702 illustrates the timing of a first communicationprotocol where the Sensor Electronics Unit 6 sends communicationsindicative of the measurements taken to one or more Display Devices20A-N. At these times, Sensor Electronics Unit 6 can also receivecommunications. For example, and without limitation, radio transmissionsuch as BLUETOOTH® can be used as the first communication protocol onCommunication Line 702 to send data indicative of blood glucosemeasurements from Sensor Electronics Unit 6 to Display Device 20. Thecommunications can occur periodically, such as occurring at Times 708,710, 712, 714.

In some implementations, the time between each sequential Times 708,710, 712, 714 can be 5, 10, 15, 20 minutes or more as desired. At eachof Times 708, 710, 712, 714, a Sensor Electronics Unit 6 can sendcommunications along Communication Line 702. As a non-limiting example,at Time 708, a communication window between Sensor Electronics Unit 6and Display Device 20 can initiate with Rising Edge 716. SensorElectronics Unit 6 can then actively send/receive communications for apredetermined amount of time on Edge 718, where the communication windowis open. For example, and without limitation, the predetermined amountof time can be 10, 15, 20, 25, 30, 35, 40 or any desired number ofseconds. The communication window can then close with Falling Edge 720.In some cases, the amount of time can be related at least in part to theamount of data transmitted and/or the transmission time for that data.

By way of illustrative example, and without limitation, Times 708, 710,712, 714, and the relationship between them, can be indicative of thefrequency in which communications occur, which can be variable based onuser-defined settings and/or predetermined transmission frequenciesbased on activities. For example, and without limitation, a period of 5minutes or less between two consecutive measurement transmissions (e.g.,between Time 708 and Time 710, Time 710 and Time 712, and/or Time 712and Time 714) can be used when the user desires to have very regularand/or frequent data points on his/her blood glucose levels. Suchregular and/or frequent data points can be desirable when the user isgoing through normal activities such as walking, working, routineexercise, driving, etc. so that he/she can analyze trends in thoseactivities. As another non-limiting example, a period of 20 minutes ormore between two consecutive measurement transmissions (e.g., betweenTime 708 and Time 710, Time 710 and Time 712, and/or Time 712 and Time714) can be used when a user does not desire many data points. Forexample, and without limitation, a user's blood glucose levels may berelatively normal or stabilized. By not transmitting measurement data asfrequently, a user can extend the life of Sensor Electronics Unit 6and/or Continuous Analyte Sensor 8. As another non-limiting example,periods of time between two consecutive measurement transmissions (e.g.,between Time 708 and Time 710, Time 710 and Time 712, and/or Time 712and Time 714) can be dynamic and/or variable based on activities and/orconditions. For example, a shorter period of time can be used if aclinically risky situation is detected, such as conditions indicative atleast in part of hyperglycemic or hypoglycemic events. In thosesituations, Sensor Electronics Unit 6 and/or Display Device 20 candetect when a user's blood glucose levels fall below a hypoglycemicglucose level threshold or above a hyperglycemic glucose levelthreshold. In those cases, Sensor Electronics Unit 6 can increase itsconnection establishment frequency such that the period of time betweentwo consecutive measurement transmissions is reduced. As anotherexample, Sensor Electronics Unit 6 and/or Display Device 20 can detectwhen a user is sleeping and transmit measurement data more frequently asthere may be risks for diabetics of having a hypoglycemic state whilesleeping. The period of time between consecutive measurementtransmissions can also be variable on a predetermined schedule, such astransmitting more frequently during meal times. In some cases, the timeperiod between consecutive measurement transmissions can be set bysending a command and the time period between those consecutivemeasurement transmissions over NFC or RFID so that a user can tap (orbring in substantially close proximity) a Display Device 20 to SensorElectronics Unit 6. Advantageously, this can allow a user to set thefrequency of measurement transmission on demand.

FIG. 7B illustrates an example timing diagram of Sensor Electronics Unit6 showing signal processing that can occur between the communications ofthe first communication protocol of FIG. 7A. For example, and withoutlimitation, Sensor Electronics Unit 6 can perform signal processing onmeasurement data periodically between communications, such ascommunications on Communication Line 702. Signal Processing Line 722illustrates the timing of the signal processing. By way of illustrativeexample, and without limitation, communication windows can open at Times708, 710, as described with respect to FIG. 7A. Between Times 708, 710,a signal processor (e.g., a processor substantially similar to SignalProcessor 308) can perform signal processing at Times 724, 726, and/orother predefined times. Such signal processing can include any signalprocessing described in this disclosure. In some cases, the signalprocessing can include data aggregation where the measurements takensince the last communication are compiled and processed to determine,e.g., analyte measurement trends, blood glucose measurements, and/orother indicia of blood glucose levels and/or the health of the user ofSensor Electronics Unit 6. In some cases, a conversion function can beused to convert measured unprocessed data into processed data, such asestimated glucose values. The signal processing can also determine thestate of the user (e.g., normal, hypoglycemic, hyperglycemic) andinitiate an alarm and/or notification if there are any health concerns.

FIG. 7C illustrates an example transmission from Sensor Electronics Unit6 using a second communication protocol to initiate a communicationusing the first communication protocol from the example timing diagramof FIG. 7B. For example, and without limitation, Transmission 732 canutilize a second communication protocol, such as a communicationprotocol utilizing an RF field, including but not limited to NFC orRFID, on Communication Line 706. Transmission 732 can further include acommand to initiate communication along the first communication protocol(e.g., utilizing a radio transmission such as BLUETOOTH®) whose timingis represented by Communication Line 702. Other transmissions inTransmission 732 can include those associated with a retrieve dataaction, such as Action 617. That communication can occur after TimeDelay 736, which can be a predetermined delay (e.g., 5, 4, 3, 2, 1, orless seconds). For example, and without limitation, Waveform 734 canrepresent an additional communication window opening. In someimplementations, this additional communication window opening can sendaggregated measurements as processed by Sensor Electronics Unit 6 unitprior to Transmission 732. By way of illustration, and withoutlimitation, data aggregated by processing initiated at Time 724 can besent during Transmission 734 in response to Transmission 732.Transmission 734 can occur after Time Delay 736 from Transmission 732.Advantageously, in some implementations, Transmission 734 can occurwithout altering and/or shifting the schedule communication windowopenings on Communication Line 706. This ability to not alter and/orshift the schedule of communications can allow a user to receive/senddata without then having to wait for the whole communication timing(e.g., the time period between Time 710 and Time 708) for the nextcommunications, as may be the case had the communication schedule beenaltered.

In other implementations, instead of Transmission 734, a transmission ofdata can utilize communications using the second communication protocol.For example, and without limitation, Display Device 20 can sendTransmission 732 to Sensor Electronics Unit 6 to send recent data.Sensor Electronics Unit 6 can then return data to Display Device 20using the second communication protocol.

C. Starting or Stopping Sensor Sessions

In some cases, a user may desire to start a new sensor session and/orend a prior sensor session. For example, and without limitation, in somecases, Continuous Analyte Sensor 8 can have a certain life for usage ona user. By way of illustrative example, and without limitation, a usermay use Continuous Analyte Sensor 8 for 1, 2, 3, 4, 5, 6, 7, 8, 9, 10,14 or more days, or any amount of time in which Continuous AnalyteSensor 8 was constructed to function, before changing Continuous AnalyteSensor 8. For example, and without limitation, the amount of timeContinuous Analyte Sensor 8 can function can be called a sensor session.Starting or stopping a sensor session can be performed in combinationwith other actions, such as one or more of Actions 613. These actionscan be performed in a queue, such as Action Queue 630.

By way of illustrative background, components of a Sensor ElectronicsUnits 6 may be replaced periodically. For example, and withoutlimitation, Continuous Analyte Sensor 8 may be attached to a SensorElectronics Unit 6, where it can be desirable to replace ContinuousAnalyte Sensor 8 periodically (e.g., every 7-30 days). SensorElectronics Unit 6 can be configured to be powered and/or active formuch longer than Continuous Analyte Sensor 8, where Sensor ElectronicsUnit 6 can have power for 1, 2, 3, 4, 5, 6 or more months until itspower supply (e.g., a battery and/or Power Supply 303) runs out of life.Replacing these components can be difficult and costly, including timeand monetary costs for assistance from trained personnel. Reducing thereplacement of such components, including the battery if replaceable,significantly improves the convenience of Sensor Electronics Unit 6 to auser.

In some implementations, when the Sensor Electronics Unit 6 is used forthe first time (or reactivated once a battery has been replaced in somecases), it can be connected to Continuous Analyte Sensor 8. DisplayDevice 20 and Sensor Electronics Unit 6 can initially establishcommunications when Sensor Electronics Unit 6 is first used orre-activated (e.g., the battery is replaced). Once Display Device 20 andSensor Electronics Unit 6 have established communication, Display Device20 and Sensor Electronics Unit 6 may periodically and/or continuously bein communication over the life of several sensors (e.g., ContinuousAnalyte Sensor 8) until, for example, the battery or the entirety ofSensor Electronics Unit 6 is replaced. Each time the sensor is replaced,notifications of a new sensor can be sent/exchanged via communicationprotocols (e.g., any communication protocol described in thisdisclosure) between the Sensor Electronics Unit 6 and Display Device 20.

In accordance with some implementations, Sensor Electronics Unit 6 cangather and/or process sensor measurements from Continuous Analyte Sensor8 and periodically send sensor information representative of the sensormeasurements to Display Device 20. Measurements can be gathered andtransmitted over the life of Continuous Analyte Sensor 8 (e.g., in therange of 1 to 30 days or more). In some cases, measurements can betransmitted often enough to adequately monitor analyte levels, such asblood glucose levels. Rather than having the radio-frequency (“RF”)circuitry of Sensor Electronics Unit 6 and Display Device 20continuously communicating, Sensor Electronics Unit 6 and Display Device20 may regularly and/or periodically establish a communication channelbetween them. Thus, Sensor Electronics Unit 6 can communicate wirelesslywith Display Device 20 at predetermined time intervals. The duration ofthe predetermined time intervals can be selected to be long enough sothat Sensor Electronics Unit 6 does not consume an undesired amount ofenergy/power by transmitting data too frequently, yet frequent enough toprovide substantially real-time sensor information (e.g., measuredanalyte values) to one or more of display devices for output to a user.As described in this disclosure, this transmission of data can occur atpredetermined time intervals and/or irregularly/aperiodically asdesired.

A user may desire to start a sensor session after connecting a newsensor (e.g., Continuous Analyte Sensor 8) to Sensor Electronics Unit 6.In starting a new sensor session, Sensor Electronics Unit 6 (and in somecases a Display Device 20) recognizes that a new sensor is being usedand can initialize and calibrate that sensor. Similarly, a user maydesire to stop a sensor when the user desires to replace the sensor.Also, in some cases, a user may not start/end a sensor session whileconnecting/disconnecting from a sensor. Instead, by way of non-limitingexamples, the user may desire to start/stop a user session tosynchronize data collection to a particular time, stop collecting data,and/or reconnect after a poor connection between a Sensor ElectronicsUnit 6, sensor (e.g., Continuous Analyte Sensor 8), and/or DisplayDevice 20. Having such ability can allow the user to get data morequickly and/or have a better user experience. In some cases, stopping asensor session may be desirable where the sensor is no longer collectingdata and/or the sensor is collecting bad data. Stopping the sensorsession at this time can prevent bad data from continuing to beprocessed by Sensor Electronics Unit 6 and/or prevent Display Device 20from alerting a user that no data and/or bad data is being collected.

However, in some implementations, starting/stopping sensor sessions canbe unintuitive and/or difficult for a user. For example, and withoutlimitation, returning to FIG. 7A, Communication Line 702 illustrates thetiming of a first communication protocol where the Sensor ElectronicsUnit 6 opens a communication window and can send/receive communicationsindicative of the measurements taken with a Display Device 20. Forexample, and without limitation, the first communication protocol canutilize radio transmission such as BLUETOOTH®, which can be used to senddata indicative of blood glucose measurements. The communication windowscan open periodically, such as occurring at Times 708, 710, 712, 714. Inthis example, where a user desires to start or stop a sensor session,the user can use a second communication protocol, different than thefirst communication protocol. The second communication protocol caninclude a communication protocol creating an RF field, such as NFC orRFID.

FIG. 7D illustrates an example timing diagram showing a transmissionover a second communication protocol that stops a sensor session, suchas the sensor session referenced in FIG. 7A. In this illustrativeexample, Transmission 742 can utilize a second communication protocol,such as a communication protocol creating an RF field, including NFC orRFID, along Communication Line 706. Transmission 742 can includecommands or instructions to stop measurements and/or stop sending dataover a radio transmission, such as BLUETOOTH®. The receipt ofTransmission 742 can stop measurements and communications along thefirst communication protocol on Communication Line 702 (e.g., closingcommunications over Communication Line 702). In some implementations,there can be a delay after Transmission 742 before measurements andcommunications along the first communication protocol stop. This delaycan be Time Delay 746, which can be a predetermined delay (e.g., 5, 4,3, 2, 1, or less than 1 second) set by a user or automatically by SensorElectronics Unit 6 and/or Display Device 20. After Time Delay 746,measurements on Measurement Line 704 can turn off.

FIG. 7E illustrates an example timing diagram showing the timing of atransmission over a second communication protocol that starts a sensorsession. In this illustrative example, Transmission 752 can utilize asecond communication protocol, such as a communication protocol creatingan RF field, including NFC or RFID, along Communication Line 706. Thereceipt of Transmission 752 can start measurements and communicationsalong the first communication protocol along Communication Line 702. Insome implementations, there can be a delay after Transmission 752 beforemeasurements and communications along the first communication protocolstart. This can be Time Delay 756, which can be a predetermined delay(e.g., 5, 4, 3, 2, 1, or less than 1 second) set by a user orautomatically by Sensor Electronics Unit 6 and/or Display Device 20.After Time Delay 756, measurements on Measurement Line 704 can turn on.

D. Pairing Using Multiple Communication Protocols

In some implementations, one communication protocol can be used toinitiate a pairing using another communication protocol. Such pairingcan be performed as part of Action 615 and/or as a separate action. Aswas mentioned in this disclosure, a pairing action (e.g., Action 615and/or other pairing action described in this disclosure) can beperformed by Pairing Unit 655 and in combination with other actions,such as one or more of Actions 613. These actions can be performed in aqueue, such as Action Queue 630. Such pairing ability can beadvantageous in improving user experience. For example, and withoutlimitation, some communication protocols have extensive pairing and/orauthentication procedures. As a non-limiting example, radio transmissionsuch as BLUETOOTH® can utilize a handshaking procedure where a device(e.g., Display Device 20) sends authentication information and isselected from a list of available devices. Having procedures with toomany steps can detract from the user experience and also drain batterylife and bandwidth with excessive communications.

By way of background, and as a non-limiting example, where DisplayDevice 20 can have a unique address, such as a unique 48-bit addresswhich can be represented as a 12-digit hexadecimal value. The address,or a portion of the address, can be used as an identifier for otherdevices with the same radio transmission, such as BLUETOOTH®, wherethose other devices also can also have an address for connection forcommunication. BLUETOOTH® devices can also have user-friendly namesgiven to them to be seen in a display.

In this background example, for BLUETOOTH® and substantially similarradio transmission protocols, the connection process using BLUETOOTH®can have multiple steps. The first step can be an inquiry, where twoBLUETOOTH® devices (e.g., a first device and second device by way ofillustration) connecting for the first time run an inquiry to discoverthe other. The first device can send out a request, and the seconddevice responds to the request with its address and possibly otherinformation (e.g., its user friendly name or any desired information).The inquiry request can include the address of the first device, or theaddress information can be sent in a separate transmission. The nextstep is a paging process where the devices use the addresses obtained inthe inquiry step to form a connection. The next step is the connectionstep, where the devices actually connect.

In some cases, during an initial connection, the two devices can bepaired using an authentication process where a user validates theconnection between the first and second devices. The flow of theauthentication can vary, depending on the user interfaces of thedevices. Sometimes pairing can be the click of the button, the enteringof a numeric code, entering a common pin, entering an alphanumericstring, etc.

Because the BLUETOOTH® pairing process takes so many steps, and mayprompt a user to enter information or take other actions, it can takeaway from the user experience. There is a need to simplify thisprocedure for the pairing CGM devices so that users can more easilymonitor their glucose levels on their devices. Also, Sensor ElectronicsUnit 6 may not have user interfaces, which can make user initiatedpairing over some communication protocols, such as radio transmission(e.g., BLUETOOTH®), more challenging. In many cases, with communicationprotocols such as BLUETOOTH®, a user may initiate and/or confirmpairings using a user interface of Display Device 20. With an RF fieldsuch as NFC or RFID, a user may just place Display Device substantiallynext to the Sensor Electronics Unit 6. This ability of NFC or RFID maybe advantageous when Sensor Electronics Unit 6 does not have a userinterface.

FIG. 8 illustrates an example flow chart showing how one communicationprotocol can be used to facilitate pairing for communication usinganother communication protocol. Process 800 can be performed by SensorElectronics Unit 6 and/or Display Device 20 used with a CGM system.

In Block 802, a first device (e.g., Sensor Electronics Unit 6 or DisplayDevice 20) can send an address, pairing information (e.g., timinginformation, encryption key, authentication information, advertisingparameters, address, make/model, name, GAP, IRK, etc.), commands, and/orother information to a second device (e.g., Sensor Electronics Unit 6 orDisplay Device 20) using a second communication protocol. In some cases,the second communication protocol can utilize an RF field, such as NFCor RFID. In particular, NFC or RFID may be advantageous because they cantransmit data and/or information automatically, sometimes in seconds orfractions of a second. When in range, the address, pairing, and/or otherinformation can be sent from the device to another device.Advantageously, the limited range of NFC communication, in particular,can allow added security because only devices within its range cancommunicate via NFC. In some cases, NFC communications can be encrypted,such as using algorithms such as 128-bit or 256-bit keys and/or otherencryption algorithms complying with standards such as the AdvancedEncryption Standard (“AES”), RSA, Data Encryption Standard (“DES”),Triple DES, and the like.

In some implementations Block 802 can include sending encryptioninformation. For example, and without limitation, encryption can be anencryption associated with a first communication protocol (e.g.,BLUETOOTH® encryption) or other encryption schemes, such as, withoutlimitation, using algorithms such as 128-bit or 256-bit keys and/orother encryption algorithms complying with standards such as the AES,RSA, DES, Triple DES, and the like.

In some implementations, Block 802 can include sending parameters, whichcan include frequency of advertising, the sequence of advertising (e.g.,which devices are advertised to in what order and with what signals),type of Display Device 20 to be paired, and/or other pairinginformation. Advantageously, this can facilitate the pairing of DisplayDevice 20 and Sensor Electronics Unit 6, and allow battery managementwherein excessive advertising can be reduced.

Similarly, in Block 804, the second device can receive address, pairing,commands, and/or other information from the first device using thesecond protocol. The pairing information can include timing information,encryption key, authentication information, advertising parameters,address, make/model, name, GAP, IRK, and the like.

In Block 806, the first device can then pair with the second device forcommunication over the first communication protocol, which in someimplementations can be a radio transmission such as BLUETOOTH®.

By way of illustrative example, Process 800 can be part of atap-to-initiate NFC protocol where a user with Display Device 20 canconnect Display Device 20 to Sensor Electronics Unit 6 of a CGM systemby tapping (or bringing in substantially close proximity) Display Device20 to Sensor Electronics Unit 6. This tap can use an RF field protocol,such as NFC or RFID, as the second communication protocol. This secondcommunication protocol can then facilitate Display Device 20 and SensorElectronics Unit 6 to pair to communicate using a first communicationprotocol, such as BLUETOOTH®.

In some cases, Process 800 (which can be called out-of-band pairing) canbe used to conserve power over conventional pairing of the firstcommunication protocol. For example, and without limitation, theadvertising and connecting of Display Device 20 to Sensor ElectronicsUnit 6 using radio transmission such as BLUETOOTH® can drain the batterylife of Sensor Electronics Unit 6. In some cases, Sensor ElectronicsUnit 6 can advertise using radio transmission such as BLUETOOTH® fordifferent lengths of time depending on the type Display Device 20attempting to connect. As non-limiting example, the advertising andconnecting time using BLUETOOTH® for a specialized receiver can beshorter (e.g., about 7 seconds) as compared to the advertising andconnecting time (e.g., 20 seconds) for a mobile device. As aconsequence, energy savings can occur when NFC or RFID is used to pairbecause of the shorter connecting time.

By way of illustrative example, instead of the advertising andconnecting time and power consumption associated with the radiotransmission (e.g., BLUETOOTH®), NFC or can be used to initiate thepairing for the radio transmission. If used in a tap-to-initiatefashion, connecting Display Device 20 can establish a connection ondemand without incurring (and/or using less than) the power consumptionassociated with standard radio transmission advertising and connecting.

E. Setting the White List and/or Bonding List

In some implementations, actions can be taken over a communicationprotocol to set and/or manipulate the white list and/or bonding list ofSensor Electronics Unit 6. In cases where NFC is used, these actions caninclude Action 618 and/or similar actions, where some actions canutilize Set White/Bonding List Unit 658. The following illustrativeexamples described in reference to white lists and bond lists can bepart of Action 618 and/or separate actions, and/or utilize SetWhite/Bonding List Unit 658. As was mentioned in this disclosure, asetting white/bonding list action (e.g., Action 618 and/or other actionsdescribed in this disclosure setting, adding to, removing from, and/ormanipulating a white list and/or bonding list) can be performed incombination with other actions, such as one or more of Actions 613.These actions can be performed in a queue, such as Action Queue 630.

FIG. 9A-F illustrates example manipulations of white lists and/orbonding lists using a plurality of communication protocols. FIG. 9Aillustrates an example White List 906 and Bonding List 914 that can beused for pairing Sensor Electronics Unit 6 and Display Device 20A byusing two or more communication protocols. Sensor Electronics Unit 6 cancommunicate with Display Device 20A as described in Process 800. Asdescribed in Process 800, a second communication protocol can be used toallow Sensor Electronics Unit 6 and Display Device 20A to send/receivedaddress, pairing, and/or other information from each other. As a resultof the exchange, Sensor Electronics Unit 6 and Display Device 20A cancommunicate using a first communication protocol, such as, withoutlimitation, a first communication protocol using radio transmission suchas BLUETOOTH®.

For the radio transmission (e.g., BLUETOOTH®) connection, Display Device20A can be listed on White List 906 of Sensor Electronics Unit 6 when itis paired with Sensor Electronics Unit 6. White List 906 can have apredetermined number of slots, such as Slot 908A, where the pairinginformation from Display Device 20A can be saved into that slot. Theinformation from White List 906 can also be stored on Bonding List 914.For example, and without limitation, the information for Display Device20A stored in Slot 908A of White List 906 can also be stored in Slot910A of Bonding List 914.

FIG. 9B illustrates multiple example Display Devices 20A,C connectingusing a second communication protocol as reflected in White List 906 andBonding List 914 illustrated in FIG. 9A. For the radio transmission(e.g., BLUETOOTH®) connection, Display Device 20C can also be listed onWhite List 906 of Sensor Electronics Unit 6. The pairing information(e.g., address, make/model, name, GAP, IRK, etc.) for Display Device 20Ccan be stored in a different slot, such as Slot 908B, from the pairinginformation for Display Device 20A, which was stored in Slot 908A. Thepairing information for Display Device 20C can also be stored in a slotin Bonding List 914, such as Slot 910B.

FIG. 9C illustrates an example white list and bonding list being updatedwhen Sensor Electronics Unit 6 and Display Device 20A are unpaired usingthe second communication protocol. Advantageously, using a secondcommunication protocol, such as an RF field (e.g., NFC or RFID), canallow a user to remove Display Device 20A (or any other display device,such as Display Device 20C) from a white list (e.g., White List 906)dynamically and on-demand. This can result in power savings in somesituations. By way of illustrative example, Sensor Electronics Unit 6can advertise to a display device on White List 906. However, if thatdisplay device is no longer in range and/or no longer desirable for use,Sensor Electronics Unit 6 potentially wastes energy undesirably intrying to make that connection. Also, advantageously, removing a firstdisplay device from White List 906 can prevent that first display devicefrom inadvertently connecting if such connection would be undesirable.For example, and without limitation, a user may want to connect a seconddisplay device to Sensor Electronics Unit 6, and having the firstdisplay device connect to Sensor Electronics Unit 6 may prevent thesecond display device from connecting by taking its position in WhiteList 906.

By way of example illustration, and without limitation, SensorElectronics Unit 6 can use the second communication protocol, as alsodescribed with reference to FIGS. 9A-B, to remove Display Device 20Afrom White List 906, and consequently, from active communication withSensor Electronics Unit 6. In some implementations, Display Device 20Acan send a command to Sensor Electronics Unit 6 telling SensorElectronics Unit 6 to remove Display Device 20A from Slot 908A. In somecases, this can leave an empty spot in White List 906.

Bonding List 914 may act independently from White List 906. Just becauseDisplay Device 20A was removed from White List 906 does not mean it willbe removed from Bonding List 914. Bonding List 914 can store DisplayDevice 20A's pairing information for later use. In some cases, whereBonding List 914 has utilized all its open slots, pairing information inone or more slots of Bonding List 914 may be deleted. Bonding List 914can be stored in an application (e.g., a mobile application downloadedfrom an entity that created and/or owns and/or licenses the app, and/oran app store such as from APPLE, INC. or GOOGLE INC., or other) on oneor more of Sensor Electronics Unit 6 and Display Devices 20A,C. In somecases, this deletion can be accomplished by Display Device 20A sendingover the second communication protocol at least a command/request toremove Display Device 20A's pairing information from Bonding List 914.This removal can be desirable where a user does not want SensorElectronics Unit 6 to communicate with Display Device 20A anymore, anddoes not want to risk Display Device 20A connecting. Removing DisplayDevice 20A from Bonding List 914 advantageously reduces that risk ofundesired communication/connection by removing the pairing informationfrom memory.

FIG. 9D illustrates an example where a second communication protocol canbe used to add Display Device 20D to White List 906 of a firstcommunication protocol, and remove Display Device 20C from that sameWhite List 906. Initially, pairing information for Display Device 20Acan be stored in Slot 908A and pairing information for Display Device20C can be stored in Slot 908B, and Display Device 20C and SensorElectronics Unit 6 can be paired for communication using the secondcommunication protocol. Display Device 20D can pair with SensorElectronics Unit 6 to communicate over the first communication protocolby using a second communication protocol, such as a communicationprotocol using an RF field (e.g., NFC or RFID) as described in Process800. In some cases, the pairing of Display Device 20D to SensorElectronics Unit 6 can cause Display Device 20D to replace anotherdisplay device paired to Sensor Electronics Unit 6. This can bedesirable when all slots in White List 906 are filled and/or the userdesires to pair Display Device 20D to Sensor Electronics Unit 6. In someimplementations, Display Device 20D can also send a command via thesecond communication protocol to Sensor Electronics Unit 6 instructingSensor Electronics Unit 6 to replace the pairing information of DisplayDevice 20C on White List 906 with pairing information for Display Device20D. In some implementations, the command can include instructions thatcauses the Sensor Electronics Unit 6 to add Display Device 20D to WhiteList 906. In some cases, based at least in part on the type of DisplayDevice 20D (e.g., receiver, mobile device, etc.), Sensor ElectronicsUnit 6 can replace a display device on White List 906 of the same devicetype. In some implementations, the command may include instructions thatmay cause the Sensor Electronics Unit 6 to send Display Device 20Dinformation indicative of at least the contents of White list 906,including Slot 908B. Sensor Electronics Unit 6 can then send suchinformation indicative of White List 906's contents to Display Device20D. Display Device 20D can then, through user input or automatically(e.g., based on device type or learned pattern, such as a userdisconnecting a device at certain times of day), choose to remove thepairing information of Display Device 20C from Slot 908B and add thepairing information of Display Device 20D. As illustrated in FIG. 9D,pairing information for Display Device 20D can replace pairinginformation for Display Device 20C in Slot 908B.

FIG. 9E illustrates an example where the second communication protocolis used to reorder White List 906 illustrated in FIG. 9B. In someimplementations, Sensor Electronics Unit 6 can communicate to paireddisplay devices, (e.g., any paired Display Devices 20A-N), serially. Inother words, it can communicate to one display device first and thensequentially to the next display device.

By way of illustrative example, FIG. 9G illustrates sequentialcommunication windows for communication between Sensor Electronics Unit6 and display devices in Slots 908A-N. Communications between SensorElectronics Unit 6 and display devices in Slots 908A-N can occur inCommunication Windows 972A-N. Communication Windows 972A-N can each be aperiod of time where Sensor Electronics Unit 6 can connect to therespective display devices in Slots 908A-N and communicate with thosedisplay devices. Each Communication Windows 972A-N can be set (e.g., bya user or automatically by Sensor Electronics Unit 6) independently ortogether. For example, the period of time for each of CommunicationWindows 972A-N can be set independently in some cases. In other cases, aplurality of Communication Windows 972A-N can be set as the same periodof time. In other cases, all of Communication Windows 972A-N can be setas the same period of time. In any of these cases, the period of timecan be 5, 10, 15, 20, 25, 30, or more seconds. The period of time canalso be set based at least in part on the time it takes to connect to adisplay device, the importance of the connection, and/or other factors.For example, the time it takes to connect to a display device can varyby device type and the communication protocol used. By way ofillustration, a specialized receiver can be specifically configured toconnect to Sensor Electronics Unit 6 and can send/receive pairinginformation faster than a generalized device, such as a mobile device.Accordingly, the specialized receiver may be in one of CommunicationWindows 972A-N that has been set with a smaller period of time. In somecases, the period of time for one of Communication Windows 972A-N thatcorresponds with a preferred device can be longer because a longerperiod of time can allow for more communication attempts in case thereare any dropped and/or missed communications.

Because Sensor Electronics Unit 6 can communicate sequentially to thedisplay devices in Slots 908A-N (e.g., where Sensor Electronics Unit 6first communications to the display device in Slot 908A, then to thedisplay device in Slot 908B, and so on and so forth), there can be atemporal difference between when display devices in Slots 908A-N receivemessages. There can also be reliability differences (and/or robustnessdifferences) between communications between Sensor Electronics Unit 6and the display devices in each of Slots 908A-N. In some cases, thedisplay device in Slot 908A that receives information first can bedesignated the primary display device, the display device in Slot 908Bcan be the secondary display device, the display device in Slot 908C canbe the tertiary display device, and so on and so forth. In some cases,it may be desirable to switch the order of which display device is inwhich of Slots 908A-N. As an illustrative example, and withoutlimitation, it may be desirable to switch the secondary display deviceto the primary display device, and consequently the display device inSlot 908B to Slot 908A.

In some cases, one or more of Display Devices 20A-N can communicate withSensor Electronics Unit 6 to change the designation of one or moreDisplay Devices 20A-N. Returning to FIG. 9E, by way of non-limitingexample, and without limitation, the pairing information for DisplayDevice 20C can be initially stored in Slot 908B and the pairinginformation for Display Device 20A can initially be stored in Slot 908A.Display Device 20C can communicate with Sensor Electronics Unit 6 usinga second communication protocol, such as a communication protocol usingan RF field, such as NFC or RFID. Through the second communicationprotocol, Display Device 20C can send a command to Sensor ElectronicsUnit 6 to move it to Slot 908A and move the pairing information in Slot908A (e.g., the pairing information of Display Device 20A) to anotherslot, such as Slot 908B. In some implementations, the command cancomprise a request to designate Display Device 20C to a particularstatus (e.g., primary, secondary, tertiary, etc.). Accordingly, SensorElectronics Unit 6 can then switch Display Device 20C from Slot 908B toSlot 908A, and Display Device 20A from Slot 908A to Slot 908B based atleast in part on the determination of Sensor Electronics Unit 6 thatSlot 908A corresponds to the requested particular status. In making thatswitch, Sensor Electronics Unit 6 can also switch Display Device 20A toSlot 908B based at least in part on a determination that because DisplayDevice 20C is switching to Slot 908A, Display Device 20A should switchto Slot 908B to provide for the appropriate priority. In someimplementations, the command can comprise an interrogatory asking SensorElectronics Unit 6 to send Display Device 20C information indicative ofat least the contents of White List 906, including Slot 908B. SensorElectronics Unit 6 can then send such information indicative of WhiteList 906's contents to Display Device 20C. Display Device 20C can then,through user input or automatically (e.g., based on device type orlearned pattern, such as a user's usage of a display device as theprimary display device at certain times of day), choose to switch thepairing information in Slot 908B and Slot 908A.

In some implementations, the command to reorder White List 906 can bepaired with another command, request, and/or action in this disclosure.For example, and without limitation, a display device can be added toWhite List 906, and White List 906 can also be reordered. There may anynumber of combinations of actions, which can be performed in a queuesuch as Action Queue 630.

FIG. 9F illustrates using the second communication protocol to moveDisplay Device 20C on the Bonding List 914 of a first communicationprotocol to White List 906 of that first communication protocol. Forexample, and without limitation, pairing information for Display Device20C can be stored in Slot 910B of Bonding List 914. Pairing informationfor Display Device 20C may not be listed in White List 906.

Using a second communication protocol, such as a communication protocolusing an RF field like NFC or RFID, Display Device 20C can send acommand to Sensor Electronics Unit 6 to move it from Bonding List 914 toWhite List 906 (e.g., to Slot 908B) of the first communication protocolof Sensor Electronics Unit 6. That first communication protocol, in somecases, can be BLUETOOTH®. Moving Display Device 20C to White List 906from Bonding List 914 can be used, in some cases, when there is amalfunction in White List 906 and information from Bonding List 914 canbe used to populate White List 906. For example, and without limitation,White List 906 can malfunction and have data corruption and may haveerrors in trying to identify and pair with Display Device 20C.Identifying information and pairing information for Display Device 20Ccan be moved from Bonding List 914 to White List 906 in suchcircumstances to allow a user to connect Display Device 20C.

In FIGS. 9A-F, even though depictions of display devices (e.g., DisplayDevices 20A,C-D) and Sensor Electronics Unit 6 have form factors forillustrative purposes, a person having ordinary skill in the art shouldappreciate that any of those display devices and Sensor Electronics Unit6 are representative of any sensor electronics unit and/or displaydevice described in this disclosure.

F. Data Transfer

In some implementations, Sensor Electronics Unit 6 may communicate witha Display Device 20 using one communication protocol. However, anothercommunication protocol can be used in certain situations. For example,in some implementations, a user may desire to connect Display Device 20to Sensor Electronics Unit 6 to collect past data, or data generated foranalysis of past events to which Sensor Electronics Unit 6 collecteddata. Such connection to collect past data can be performed at one time,or periodically as desired. For example, and without limitation, DisplayDevice 20 can be in a mode where a user may not be able to see real-timeglucose values, but can receive glucose alerts and alarms during asensor session. The data can later be downloaded by a healthcareprofessional or any user who desires to see the data using anotherdisplay device (e.g., one of Display Devices 20A-N). As anothernon-limiting example, a user may want to switch display devices (e.g.,one of Display Devices 20A-N) from another display device (e.g., anotherone of Display Devices 20A-N) that had previously been used. With thenewly connected display device, a user can download past data fromSensor Electronics Unit 6. In this case, the display device downloadingpast data may provide timing information to Sensor Electronics Unit 6 atleast in part of the period of time in which the Sensor Electronics Unit6 should send lost data. As another non-limiting example, SensorElectronics Unit 6 may reduce and/or altogether stop transmitting toconnect to Display Device 20 after a determined number of time/cycles.This can allow Sensor Electronics Unit 6 to save power, processor use,and/or other resources. As another non-limiting example, a user and/orhealthcare provider may want to periodically download data, andconsequently, may want to connect Display Device 20 to SensorElectronics Unit 6 to collect past data.

In these examples, Display Device 20 (or any other one of DisplayDevices 20A-N) may typically send/receive data and/or otherwise sendcommunications to/from Sensor Electronics Unit 6 using one communicationprotocol, such as a communication protocol using radio transmission likeBLUETOOTH®. Display Device 20 can then receive past data over anothercommunication protocol, such as an RF field like NFC and RFID. DisplayDevice 20 can first send a command to Sensor Electronics Unit 6 overeither the first communication protocol or the second communicationprotocol. Sensor Electronics Unit 6 can then send the data over thesecond communication protocol. For example, and without limitation, thisdata can be sent over a communication protocol using an RF field, suchas NFC and RFID. The second communication protocol can also re-initiatecommunication over the first communication protocol in wayssubstantially similar to processes described in this disclosure, such asthose described with reference to FIGS. 8, 9A-F.

In some implementations, NFC or RFID can be used to transmit commandand/or requests from Display Device 20 to Sensor Electronics Unit 6.These commands and/or requests can include start transmission for acommunication protocol (e.g., radio transmission such as BLUETOOTH®, orany other communication protocol described in this disclosure), pairwith display device (e.g., radio transmission such as BLUETOOTH®, or anyother communication protocol described in this disclosure), stoptransmission for a communication protocol (e.g., radio transmission suchas BLUETOOTH®, or any other communication protocol described in thisdisclosure), sleep, low power, wake-up, calibrate Sensor ElectronicsUnit 6 and/or Continuous Analyte Sensor 8, start or stop sensor session,send past data, and/or any command desirable, including those associatedwith one or more of Actions 613. In this way, in some cases,communication protocols utilizing RF fields, such as NFC or RFID, can beused to initiate transfer over data over radio transmission, such asBLUETOOTH®. This data can include, data indicative of estimated bloodglucose levels, past data indicative of blood glucose levels, pairinginformation, statuses, model numbers, error logs, communicationconditions (e.g., historical or previous communications such as thefollowing: the number of previously missed communications; a previousadvertising interval/duration budget; and/or historicaltime-until-connection associated with a particular display device), etc.

In some implementations, a second communication protocol can be used totransfer information regarding an error condition or any type of datathat would be helpful in assisting with technical support when a firstcommunication protocol is not working and/or is impaired in some form.For example, and without limitation, in some implementations, a radiotransmission such as BLUETOOTH® can be the first communication protocol.In some cases, the radio transmission capabilities of Sensor ElectronicsUnit 6, Display Device 20, or both can be impaired or broken so thatSensor Electronics Unit 6, Display Device 20, or both do not have fullcommunication capabilities over radio transmission. It may be desirableto get diagnostic and/or error condition information (e.g., an errorlog) in order to diagnose the problem. A second communication protocolusing a RF field, such as NFC or RFID, can be used to obtain thediagnostic and/or error condition information. Using the secondcommunication protocol can be advantageous in that it allows thediagnostic and/or error condition information to be pulled on demandinstead of waiting for the communication timing of the firstcommunication protocol, if the first communication protocol can evensend that information. By way of illustrative example, Display Device 20can send a command to Sensor Electronics Unit 6 over a communicationprotocol using an RF field, such as NFC or RFID. Sensor Electronics Unit6 can then send the diagnostic and/or error condition information usingthat same communication protocol. In some cases, Display Device 20 canthen further transfer this information to a server (e.g., a network,cloud, etc.) via a communication protocol, such as cellular connection,Wi-Fi or any communication protocol described in this disclosure.

In some cases, it can be desirable to receive data from SensorElectronics Unit 6 when the battery of Sensor Electronics Unit 6 is lowor dead. In some implementations, a communication protocol can be usedto retrieve that data, such as, without limitation data indicative ofestimated blood glucose levels, past data indicative of blood glucoselevels, pairing information, statuses, model numbers, error logs, etc.For example, and without limitation, a communication protocol using anRF field, such as NFC or RFID, can use the energy of the Display Device20 to power the transmission of Sensor Electronics Unit 6 over that samecommunication protocol. By way of illustrative example, where NFC is thecommunication protocol, Display Device 20 can create an RF field usinginduction. Sensor Electronics Unit 6 can have an NFC tag that storesdata. Accordingly, the Display Device 20 can have an NFC reader that canread the NFC tag even when Sensor Electronics Unit 6 has little or nopower. In some implementations, the use of a communication protocol byDisplay Device 20 can actually power Sensor Electronics Unit 6 unit tosend data. By way of illustrative example, and without limitation, themagnetic inductance of the RF field created by Display Device 20 usingan NFC communication protocol can allow for inductive charging, or thetransfer of energy wirelessly from Display Device 20 to SensorElectronics Unit 6. This energy can be used by Sensor Electronics Unit 6to power data transfer using an RF field, such as NFC, or anothercommunication protocol. In some implementations, this energy can be usedby Sensor Electronics Unit 6 to power the circuitry (e.g.,application-specific integrated circuit (“ASIC”) and/or other hardware)of Sensor Electronics Unit 6 to recover data and/or this energy can beused to power a radio transmission protocol, such as BLUETOOTH®. Theradio transmission protocol can then transmit data from SensorElectronics Unit 6 to Display Device 20.

Advantageously, there can be situations where a user desires to retrievesuch data from their Sensor Electronics Unit 6 after Sensor ElectronicsUnit 6 has low or no battery life. For example, and without limitation,a user could send his/her Sensor Electronics Unit 6 to a health provideror a third party of the end of a sensor session. At that stage, thebattery of Sensor Electronics Unit 6 may be low or depleted. The healthprovider or third party could then download the data from SensorElectronics Unit 6 using a communication protocol that uses an RF field,such as NFC or RFID. In some cases, the health provider can be promptedby Sensor Electronics Unit 6, where Sensor Electronics Unit 6 may promptthe display device of the health provider to transfer data over NFC.

As another non-limiting example, a user may wish to clone his/her SensorElectronics Unit 6 (e.g., using Action 609 and/or Clone Unit 649).Advantageously, if the user transfers the data after Sensor ElectronicsUnit 6 is out of power or has low power (e.g., little to no batterylife), he/she can transfer as much information as possible beforeswitching to a new sensor electronics unit. Accordingly, while in usingNFC and a clone action, such as Action 609, the user can then power thetransfer of data/information from Sensor Electronics Unit 6 to DisplayDevice 20 even if Sensor Electronics Unit 6 has little to no battery.

As another non-limiting example, a user may have been negligent inhis/her monitoring of his/her blood glucose level and the maintenance ofhis/her equipment. If he/she desires to get information from his/herSensor Electronics Unit 6 when it has little to no battery life, he/shecan use NFC to power that transfer.

In some implementations, a plurality of communication protocols can beused where some types of communications are sent over one type ofcommunication protocol and other types of communications are sent overanother type of communication protocol.

By way of illustrative example, and without limitation, NFC can be usedto send all commands and/or requests from a Display Device 20 to SensorElectronics Unit 6. These commands and/or requests can include starttransmission for a communication protocol (e.g., radio transmission suchas BLUETOOTH®, or any other communication protocol described in thisdisclosure), pair with Display Device 20 (e.g., radio transmission suchas BLUETOOTH®, or any other communication protocol described in thisdisclosure), stop transmission for a communication protocol (e.g., radiotransmission such as BLUETOOTH®, or any other communication protocoldescribed in this disclosure), calibrate Sensor Electronics Unit 6 withContinuous Analyte Sensor 8, send past data, and/or any commanddesirable, including those associated with one or more of Actions 613.NFC can also be used to configure settings of the Sensor ElectronicsUnit 6, such as its transmission parameters, advertising (e.g.,broadcasting, beaconing, stealth mode, etc.), timings, etc.Advantageously, NFC can provide a secure and intuitive way for a user tosend these commands and/or requests. The range limitation of NFC canlower the risk of unauthorized display devices sending commands and/orrequests to Sensor Electronics Unit 6. Furthermore, the physical actionof bringing the Display Device 20 close to Sensor Electronics Unit 6 canbe intuitive for a user.

In some implementations, radio transmission such as BLUETOOTH® can beused to send all data from the Sensor Electronics Unit 6 to a DisplayDevice 20 because radio transmission can have a longer range and highertransfer speed. Also, advantageously, radio transmission communicationcan happen autonomously with Display Device 20, and also can be utilizedwithout a user actively placing a Display Device 20 next to SensorElectronics Unit 6. In some cases, the data can be transmitted inresponse to commands and/or requests sent over a communication protocolusing an RF field such as NFC or RFID. In some implementations, certaintypes of data can be sent over the RF field rather than radiotransmission. By way of illustrative example, and without limitation,some data can be considered of higher security and could have an impacton the functionality of a Sensor Electronics Unit 6/Continuous AnalyteSensor 8. It may be desirable to use a different protocol than radiotransmission to send such information. For example, and withoutlimitation, a user can send calibration data from a Display Device 20 toSensor Electronics Unit 6. This calibration data can contain dataindicative of analyte measurements, such as blood glucose levels, takenfrom another source, such as finger pricking. The data can be used tocalibrate the readings of blood glucose levels from the SensorElectronics Unit 6/Continuous Analyte Sensor 8. Such data can be sentover NFC in order to provide added security and/or to make the transfermore user-friendly. Calibration data may also be particularlyadvantageous to send over NFC because it can allow a user to adjust orupdate the calibration of Sensor Electronics Unit 6 on demand when it isconvenient and/or desirable.

In some implementations, transmissions can be split between a pluralityof communication protocols in order to further encrypt a message. Forexample, and without limitation, part of a command can be sent from aDisplay Device 20 over a first communication protocol (e.g., radiotransmission such as BLUETOOTH®) and part of the command can be sentover a second communication protocol (e.g., an RF field such as NFC orRFID). By way of illustrative example, in the cases where an RF fieldcommunication protocol and radio transmission are used, the SensorElectronics Unit 6 can perform the commanded action if it receives thepart of the command over radio transmission and the part of the commandover an RF field communication protocol. Similarly, data transmittedfrom Sensor Electronics Unit 6 can be split between an RF fieldcommunication protocol and radio transmission so that part of the datais sent over the RF field communication protocol and part of the data issent over radio transmission. In this way, a Display Device 20 would useboth the RF field communication protocol and the radio transmission toreceive all the data. As a non-limiting example, encryption informationcould be sent over an RF field communication protocol such as NFC orRFID, and then that encryption data could be used to decrypt data sentvia a radio transmission protocol such as BLUETOOTH®.

In some implementations, what kinds of transmissions are sent over whichcommunication protocol can be dependent at least in part on remainingbattery life and/or available power of Sensor Electronics Unit 6. Insome implementations, when there is battery life of Sensor ElectronicsUnit 6 is above a first predetermined threshold, one usage ofcommunication protocols can be used, where as if the battery life fallsbelow a second predetermined threshold (which may have a value equal orsubstantially equal to the first predetermined threshold or have adifferent value), a second usage of communication protocols can be used.By way of illustrative example, and without limitation, a firstpredetermined threshold can be defined in a range where the battery ofSensor Electronics Unit 6 has substantial life (e.g., above 30, 40, 50,60, or more percentage of battery life remaining, or any predeterminedpercentage as desired). When the amount of battery life is above thatfirst predetermined threshold, communications between the SensorElectronics Unit 6 and Display Device 20 can utilize radio transmissionsuch as BLUETOOTH® and/or a combination of radio transmission, such asBLUETOOTH®, and an RF field communication protocol, such as NFC or RFID.However, when the amount of battery life of the Sensor Electronics Unit6 is relative low and falls below the second predetermine threshold(e.g., less than 30% of battery life remaining), a communicationprotocol that utilizes less energy and/or saves energy can be used(e.g., an RF field communication protocol, such as NFC or RFID) forcommunications between Sensor Electronics Unit 6 and Display Device 20.Advantageously, this can allow a user to ration battery power so thatonly a certain number of actions can be performed over a communicationprotocol per day. For example, if the number of actions (e.g., 1, 5, 10,or any number of actions budgeted by a user determined at least in partby the energy consumption) performed by a first communication protocolper day is exceeded, the communications between the Sensor ElectronicsUnit 6 and Display Device 20 can switch to a second communicationprotocol. By way of non-limiting example, the first communicationprotocol can be a radio transmission such a BLUETOOTH® and the secondcommunication protocol can utilize an RF field, such as NFC or RFID. Thenumber of actions could be 5 in a day. So if the user exceeded 5communications over the radio transmission in a day, the user would thenutilize the RF field communication protocol for subsequentcommunications.

In some implementations, a transmission can be sent over onecommunication protocol, but data/information over a second communicationprotocol can be used to view the transmission. For example, and withoutlimitation, data can be sent from a Sensor Electronics Unit 6 to aDisplay Device 20 using a radio transmission protocol such asBLUETOOTH®. However, that data may not be viewable by the Display Device20 until the Sensor Electronics Unit 6 sends a decryption key over an RFfield communication protocol, such as NFC or RFID, to the Display Device20.

By way of illustrative example, and without limitation, a SensorElectronics Unit 6 may broadcast, beacon, and/or otherwise send datausing one protocol. For example, it may send data over a radiotransmission, such as BLUETOOTH®, to any device within its range. Asecond communication protocol, such as a communication protocol using anRF field like NFC or RFID can be used for a user to view thatinformation. By way of illustration, and without limitation, a SensorElectronics Unit 6 can broadcast data about a user over BLUETOOTH® toBLUETOOTH®-enabled devices within the Sensor Electronics Unit 6'sBLUETOOTH® range. These BLUETOOTH®-enabled devices can receive the dataand store the data (e.g., using a computer application). However, thedata can be encrypted and/or otherwise not viewable on theBLUETOOTH®-enabled device until the BLUETOOTH®-enabled device uses NFCor RFID to communicate with the Sensor Electronics Unit 6 to receive anencryption key, a command, and/or data that enables theBLUETOOTH®-enabled device to view the received data.

As another illustrative example, in some implementations, the SensorElectronics Unit 6 can be in broadcast mode using a first communicationprotocol using a radio transmission, such as BLUETOOTH®, wherein theradio of the Sensor Electronics Unit 6 can only send data, but cannotreceive it from a Display Device 20 (e.g., one-way data transmission).In this case, a second communication protocol using an RF field, such asNFC or RFID, can be used to send commands, such as a command opening atwo-way communication over the first communication protocol. Oncetwo-way communications are open over the first communication protocol,the Display Device 20 can send commands and/or information to the SensorElectronics Unit 6. For example, and without limitation, the DisplayDevice 20 can send calibration data and a calibration command over thefirst communication protocol to the Sensor Electronics Unit 6. Once thetwo-way communication is completed, then the Sensor Electronics Unit 6goes back into broadcast mode. Advantageously, allowing the secondcommunication protocol to open two-way communication while the SensorElectronics Unit 6 is in broadcast mode can allow the Sensor ElectronicsUnit 6 to retain the efficiency of broadcasting via broadcast mode, yetstill receive timely information and/or commands from a Display Device20.

As another illustrative example, a Sensor Electronics Unit 6 may use aradio transmission broadcast, such as a BLUETOOTH® broadcast (e.g.,beaconing and/or one-way communication), sent to Display Device 20. Thisbeacon can be sent exclusively to certain devices (e.g., in an exclusivemode) and/or can be sent only at certain times. This exclusivity can beachieved by encrypting the beacon and/or broadcasting the beacon tocertain identified display devices (e.g., identified through make,model, IP address, etc. in the beacon). For example, and withoutlimitation, a user may use different display devices at night than inthe day. In the day, he/she may go to work in an office and have mobiledevices that he/she uses there. These may be different display devicesthat he/she uses when he/she is at home. In some implementations, thebeacon can broadcast to a first set of display devices during the daywhen the user is at work and to a second set of display devices at nightwhen the user is away from work. In some cases, these radio transmissionbroadcasts can be encrypted to secure any data, commands, information,statuses, etc. sent between sensor electronics devices and displaydevices, and vice versa. In some implementations, another communicationprotocol, such as NFC or RFID can be used to transmit decryption keys todecrypt the encrypted data, commands, information, statuses, etc. WhereNFC is used, a display device that a user desires to send/receive data,commands, information, statuses, etc. can be brought in close proximityto the Sensor Electronics Unit 6. The Sensor Electronics Unit 6 may bebeaconing to the display device already, or may have yet-to-startbeaconing. The display device and Sensor Electronics Unit 6 can exchangedecryption keys (e.g., static keys and/or dynamic keys) which can thenbe used to decrypt transmissions (e.g., data, commands, information,statuses, communications, etc.) sent between the display device andSensor Electronics Unit 6.

In some cases, a Sensor Electronics Unit 6 can beacon, where it can senddata and/or invite devices within its communication range to connect. Insome implementations, a Sensor Electronics Unit 6 can beacon using afirst communication protocol and then a Display Device 20 can use asecond communication protocol to connect the Display Device 20 to theSensor Electronics Unit 6 for communication using the firstcommunication protocol. By way of illustrative example, and withoutlimitation, a Sensor Electronics Unit 6 can beacon using a radiotransmission such as BLUETOOTH®. A Display Device 20 can receive abeaconed message and be prompted to pair with the Display Device 20. TheDisplay Device 20 can then use an RF field communication protocol suchas NFC or RFID to pair the Sensor Electronics Unit 6 and Display Device20 for communication over BLUETOOTH®. Advantageously, such a pairingmechanism can simplify pairing procedures and allow users to avoid theplurality of steps involved with BLUETOOTH® pairing. Also, it may alsoprovide extra security by utilizing NFC's limited range for pairing,which may prevent unauthorized connections.

In some cases, poor connectivity over a first communication protocol,such as BLUETOOTH®, can result in too many tries to connect and droppeddata packets. Being able to intelligently switch to another, secondcommunication protocol that does not have the same connectivity issuescan be used to resynchronize the timing of the first communicationprotocol and/or be used to send the data packets.

By way of illustrative example, a first communication protocol forcommunication between a Sensor Electronics Unit 6 and a Display Device20 can be a radio transmission such as BLUETOOTH®. As desired by a user(e.g., when a user of Sensor Electronics Unit 6 and/or the DisplayDevice 20 notice connectivity issues), connections (e.g., pairing) ofthe Sensor Electronics Unit 6 and the Display Device 20 can bere-established by using a second communication protocol, such as an RFfield communication protocol (e.g., NFC or RFID).

Where radio transmission such as BLUETOOTH® is the first communicationprotocol and NFC is the second communication protocol, NFC can beparticularly helpful in re-establishing connectivity because of NFC'ssimple initiation and transmission at short ranges. As an example,Display Device 20 can send a command to the Sensor Electronics Unit 6 todisconnect. An RF field communication protocol such as NFC or RFID canalso be used by Sensor Electronics Unit 6 and/or Display Device 20 toexchange public and/or private keys for authentication and connection.

In some cases, an RF field communication protocol, such as NFC or RFID,can be used to send data from the Sensor Electronics Unit 6 to DisplayDevice 20, or vice versa, in order to send missed data. For example, andwithout limitation, over the RF field communication protocol, thereceived data packets by either the Sensor Electronics Unit 6 or DisplayDevice 20 can be compared with the sent data packets by the other ofSensor Electronics Unit 6 and Display Device 20. In some cases, theSensor Electronics Unit 6 and/or Display Device 20 can have lists ofsent, received, and/or sent but not received data packets. A processorof either the Sensor Electronics Unit 6 and/or the Display Device 20 cancompare the sent and received lists, or process the sent but notreceived list, and determine which data packets were sent but notreceived. Those data packets that were sent but not received can betransferred accordingly (e.g., from Sensor Electronics Unit 6 to DisplayDevice 20 and/or Display Device 20 to Sensor Electronics Unit 6) overthe RF Field communication protocol, or any other communication protocoldescribed in this disclosure (e.g., radio transmission such asBLUETOOTH®).

Exemplary Analyte Monitoring Systems

The following exemplary analyte monitoring systems are provided.

Analyte Monitoring System 1: An analyte monitoring system, comprising: asensor configured to take measurements indicative of analyte levels; asensor electronics unit communicatively coupled to the sensor, thesensor electronics unit configured to: receive the measurementsindicative of analyte levels from the sensor and calculate estimatedanalyte values; operate in a normal power mode and a low power mode;transmit data indicative of analyte levels when in the normal power modeusing a first communication protocol, and receive a command in the lowpower mode using a second communication protocol; and a display deviceconfigured to: transmit the command to the sensor electronics unit usingthe second communication protocol; receive data indicative of analytelevels from the sensor electronics unit using the first communicationprotocol; and wherein the sensor electronics unit is configured toswitch from the low power mode to the normal power mode in response tothe command and wirelessly connect to the display device forcommunication using the first communication protocol.

Analyte Monitoring System 2: An embodiment of Analyte Monitoring System1, wherein the low power mode is a shelf mode.

Analyte Monitoring System 3: An embodiment of Analyte Monitoring System1 or 2, wherein the command is a wake up command.

Analyte Monitoring System 4: An analyte monitoring system, comprising: asensor configured to take measurements indicative of analyte levels; asensor electronics unit communicatively coupled to the sensor, thesensor electronics unit configured to: receive the measurementsindicative of analyte levels from the sensor and calculate estimatedanalyte values, operate in a normal power mode and a low power mode,transmit data indicative of analyte levels when in the normal power modeusing a first communication protocol, and receive a command in thenormal power mode using a second communication protocol; and a displaydevice configured to: receive data indicative of analyte levels from thesensor electronics unit using the first communication protocol, andtransmit the command to the sensor electronics unit using the secondcommunication protocol; and wherein the system is configured to causethe sensor electronics unit to switch from the normal power mode to thelow power mode in response to the command and wirelessly disconnect thedisplay device from the sensor electronics unit for communication overthe first communication protocol.

Analyte Monitoring System 5: An embodiment of Analyte Monitoring System4, wherein the low power mode is a shelf mode.

Analyte Monitoring System 6: An embodiment of Analyte Monitoring System4 or 5, wherein the command is a sleep command.

Analyte Monitoring System 7: An analyte monitoring system, comprising: asensor configured to take measurements indicative of analyte levels; asensor electronics unit communicatively coupled to the sensor andconfigured to: receive the measurements indicative of analyte levels,process the received measurements, and transmit data indicative ofanalyte levels using a first communication protocol at a predefinedtime; and a display device configured to: receive data indicative ofanalyte levels sent by the sensor electronics unit using the firstcommunication protocol, and use a second communication protocol toretrieve data indicative of analyte levels from the sensor electronicsunit at least before the predefined time.

Analyte Monitoring System 8: An embodiment of Analyte Monitoring System7, wherein the processing of the received measurements by the sensorelectronics unit comprises calculating estimated analyte levels based atleast in part on the measurements.

Analyte Monitoring System 9: An analyte monitoring system, comprising: asensor configured to take measurements indicative of analyte levels; asensor electronics unit communicatively coupled to the sensor andconfigured to: receive the measurements indicative of analyte levels,process the received measurements, and transmit data indicative ofanalyte levels using a first communication protocol at a predefinedtime; and a display device configured to: receive data indicative ofanalyte levels sent by the sensor electronics unit using the firstcommunication protocol, transmit a command message via a secondcommunication protocol to stop the sensor from taking measurements, andfurther transmit a request message via the second communication protocolrequesting the sensor electronics unit to stop the transmission of thedata indicative of analyte levels using the first communicationprotocol.

Analyte Monitoring System 10: An embodiment of Analyte Monitoring System9, wherein the processing of the received measurements by the sensorelectronics unit comprises calculating estimated analyte values based atleast in part on the measurements.

Analyte Monitoring System 11: An embodiment of Analyte Monitoring System9 or 10, wherein the command message provides instructions to the sensorelectronics unit to cause the sensor to stop taking measurements.

Analyte Monitoring System 12: An embodiment of Analyte Monitoring System9, 10, or 11, wherein the display device is further configured to usethe second communication protocol to initiate the taking of measurementsby the sensor and initiate the transmission of data indicative ofanalyte levels using the first communication protocol.

Analyte Monitoring System 13: An analyte monitoring system, comprising:a sensor configured to take measurements indicative of analyte levels; asensor electronics unit communicatively coupled to the sensor, whereinthe sensor electronics unit is configured to: receive the measurementsindicative of analyte levels from the sensor and calculate estimatedanalyte values, transmit data indicative of analyte levels using a firstcommunication protocol, and receive commands using a secondcommunication protocol; and a display device configured to: receive dataindicative of analyte levels using the first communication protocol, andtransmit a data request command to the sensor electronics unit using thesecond communication protocol, wherein the sensor electronics unit sendsdata indicative of analyte levels using the first communication protocolin response to the data request command.

Analyte Monitoring System 14: An embodiment of Analyte Monitoring System13, wherein the sensor electronics unit is further configured to measurea remaining battery life of the sensor electronics unit.

Analyte Monitoring System 15: An embodiment of Analyte Monitoring System14, wherein the display device is further configured to transmit thedata request command to the sensor electronics unit using the secondcommunication protocol when the remaining battery life falls below apredetermined threshold.

Analyte Monitoring System 16: An embodiment of Analyte Monitoring System13, wherein the sensor electronics unit is configured to selectivelyreceive one or more commands over the second communication protocol andselectively transmit data over the first communication protocol.

Analyte Monitoring System 17: An embodiment of Analyte Monitoring System13, wherein the sensor electronics unit is further configured to senddata indicative of analyte levels at predetermined time intervals.

Analyte Monitoring System 18: An embodiment of Analyte Monitoring System17, wherein the sending of data indicative of analyte levels using thefirst communication protocol in response to the data request commanddoes not interfere with the sensor electronics unit sending dataindicative of analyte levels at the predetermined time intervals.

Analyte Monitoring System 19: An embodiment of Analyte Monitoring System13, 14 or 15, wherein, when the remaining battery life falls below thepredetermined threshold, the display device transmits power to thesensor electronics unit using a radio frequency field, thereby providingpower to the sensor electronics unit to send data indicative of analytelevels over the second communication protocol.

Analyte Monitoring System 20: An embodiment of Analyte Monitoring System14, wherein the sensor electronics unit is further configured to storedata indicative of analyte levels on a passive tag when the remainingbattery life falls below a predetermined threshold, and the displaydevice is further configured to read the passive tag using the secondcommunication protocol.

Analyte Monitoring System 21: An embodiment of Analyte Monitoring System13, wherein the sensor electronics unit further sends a decryption keyusing the second communication protocol in response to the data requestcommand, and the decryption key is used to decrypt the data indicativeof analyte levels sent using the first communication protocol inresponse to the data request command.

Analyte Monitoring System 22: An analyte monitoring system, comprising:a sensor configured to take measurements indicative of analyte levels; asensor electronics unit communicatively coupled to the sensor, whereinthe sensor electronics unit is configured to: receive the measurementsindicative of analyte levels from the sensor and calculate estimatedanalyte values, transmit the estimated data indicative of analyte levelsusing a first communication protocol, and receive commands using asecond communication protocol; and a display device configured to:receive data indicative of analyte levels using the first communicationprotocol, and transmit a data request command to the sensor electronicsunit using the second communication protocol, wherein the sensorelectronics unit sends a portion of the data indicative of analytelevels using the first communication protocol and another portion of thedata indicative of analyte levels using the second communicationprotocol in response to the data request command.

Analyte Monitoring System 23: An embodiment of Analyte Monitoring System22, wherein the sensor electronics unit is further configured to measurea remaining battery life of the sensor electronics unit.

Analyte Monitoring System 24: An embodiment of Analyte Monitoring System22 or 23, wherein the sensor electronics unit is further configured tocease transmission of data indicative of analyte levels when themeasured remaining battery life falls below a predetermined threshold.

Analyte Monitoring System 25: An embodiment of Analyte Monitoring System23, wherein the sensor electronics unit is further configured to utilizethe low power mode when the measured remaining battery life falls belowa predetermined low power mode threshold.

Analyte Monitoring System 26: An embodiment of Analyte Monitoring System23, 24, or 25, wherein the sensor electronics unit is further configuredto utilize the normal power mode when the measured remaining batterylife is above a predetermined normal power mode threshold.

Analyte Monitoring System 27: An embodiment of Analyte Monitoring System22 wherein the second communication protocol utilizes at least one ofnear field communication and radio-frequency identification.

Analyte Monitoring System 28: An embodiment of Analyte Monitoring System22, wherein the sensor electronics unit is further configured tocalculate estimated analyte levels based at least in part on themeasurements.

Analyte Monitoring System 29: An embodiment of Analyte Monitoring System22 wherein the display device is further configured to calculateestimated analyte values based at least in part on the measurements.

Analyte Monitoring System 30: An embodiment of Analyte Monitoring System22, wherein, after a device authentication procedure has been completed,the display device is further configured to read calibration ormanufacturing information from a passive tag incorporated into thesensor electronics unit.

Analyte Monitoring System 31: An embodiment of Analyte Monitoring System30, wherein at least a portion of the information read from the passivetag is encrypted.

In some implementations, a computing system that has componentsincluding a central processing unit (“CPU”), input/output (“I/O”)components, storage, and memory can be used to execute the monitoringsystem, or specific components and/or subcomponents of the monitoringsystem. The executable code modules of the monitoring system can bestored in the memory of the computing system and/or on other types ofnon-transitory computer-readable storage media. In some implementations,monitoring system can be configured differently than described above.

Each of the processes, methods, and algorithms described in thepreceding sections can be embodied in, and fully or partially automatedby, code modules executed by one or more computers, computer processors,or machines configured to execute computer instructions. The codemodules can be stored on any type of non-transitory computer-readablemedium or tangible computer storage device, such as hard drives, solidstate memory, optical disc, and/or the like. The systems and modules canalso be transmitted as generated data signals (e.g., as part of acarrier wave or other analog or digital propagated signal) on a varietyof computer-readable transmission mediums, including wireless-based andwired/cable-based mediums, and can take a variety of forms (e.g., aspart of a single or multiplexed analog signal, or as multiple discretedigital packets or frames). The processes and algorithms can beimplemented partially or wholly in application-specific circuitry. Theresults of the disclosed processes and process steps can be stored,persistently or otherwise, in any type of non-transitory.

As used herein, the term module or unit might describe a given unit offunctionality that can be performed in accordance with one or moreimplementations of the present application. As used herein, a module orunit might be implemented utilizing any form of hardware, software, or acombination thereof. For example, one or more processors, controllers,ASICs, PLAs, PALs, CPLDs, FPGAs, logical components, software routinesor other mechanisms might be implemented to make up a module or unit.The modules, units, circuitry, processors, etc. may be affixed to aprinted circuit board (PCB), or the like, and may take a variety offorms. In implementation, the various modules described herein might beimplemented as discrete modules or the functions and features describedcan be shared in part or in total among one or more modules. In otherwords, as would be apparent to one of ordinary skill in the art afterreading this description, the various features and functionalitydescribed herein may be implemented in any given application and can beimplemented in one or more separate or shared modules in variouscombinations and permutations. Even though various features or elementsof functionality may be individually described or claimed as separatemodules, one of ordinary skill in the art will understand that thesefeatures and functionality can be shared among one or more commonsoftware and hardware elements, and such description shall not requireor imply that separate hardware or software components are used toimplement such features or functionality.

The various features and processes described above can be usedindependently of one another, or can be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks can be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described tasks or eventscan be performed in an order other than that specifically disclosed, ormultiple can be combined in a single block or state. The example tasksor events can be performed in serial, in parallel, or in some othermanner. Tasks or events can be added to or removed from the disclosedexample implementations. The example systems and components describedherein can be configured differently than described. For example,elements can be added to, removed from, or rearranged compared to thedisclosed example implementations.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, is not generally intended to implythat features, elements and/or steps are required for one or moreimplementations or that one or more implementations necessarily includelogic for deciding, with or without author input or prompting, whetherthese features, elements and/or steps are included or are to beperformed in any particular implementation. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations, and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list. Conjunctivelanguage such as the phrase “at least one of X, Y and Z,” unlessspecifically stated otherwise, is otherwise understood with the contextas used in general to convey that an item, term, etc. can be either X, Yor Z. Thus, such conjunctive language is not generally intended to implythat certain implementations require at least one of X, at least one ofY and at least one of Z to each be present. The terms “about” or“approximate” and the like are synonymous and are used to indicate thatthe value modified by the term has an understood range associated withit, where the range can be ±20%, ±15%, ±10%, ±5%, or ±1%. The term“substantially” is used to indicate that a result (e.g., measurementvalue) is close to a targeted value, where close can mean, for example,the result is within 80% of the value, within 90% of the value, within95% of the value, or within 99% of the value. Also, as used herein“defined” can include “predefined” and/or otherwise determined values,conditions, thresholds, measurements, and the like.

While certain example implementations have been described, theseimplementations have been presented by way of example only, and are notintended to limit the scope of the inventions disclosed herein. Thus,nothing in the foregoing description is intended to imply that anyparticular feature, characteristic, step, module, or block is necessaryor indispensable. Indeed, the novel methods and systems described hereincan be embodied in a variety of other forms; furthermore, variousomissions, substitutions and changes in the form of the methods andsystems described herein can be made without departing from the spiritof the inventions disclosed herein.

What is claimed is:
 1. An analyte monitoring system, comprising: an analyte sensor configured to generate sensor data indicative of analyte levels; a sensor electronics unit communicatively connectable to the analyte sensor, wherein the sensor electronics unit is configured to: process the sensor data indicative of analyte levels from the analyte sensor to generate sensor information, transmit a first portion of the sensor information using a first communication protocol, and receive one or more commands and respond to the one or more commands using a second communication protocol; and a display device configured to: receive the first portion of the sensor information using the first communication protocol, present a user interface for user selection of at least one of the one or more commands, receive a selection of at least one of the one or more commands from a user, transmit the selected at least one of the one or more commands to the sensor electronics unit using the second communication protocol, and receive at least a second portion of the sensor information using the second communication protocol in response to the selected at least one of the one or more commands; wherein the first communication protocol uses a Bluetooth transceiver; and wherein the second communication protocol uses a Near Field (NFC) Communication transceiver.
 2. The analyte monitoring system of claim 1, wherein the sensor electronics unit is further configured to calculate estimated analyte levels based at least in part on the generated sensor data.
 3. The analyte monitoring system of claim 1, wherein the display device is further configured to calculate estimated analyte values based at least in part on the generated sensor data.
 4. The analyte monitoring system of claim 1, wherein the display device is further configured to read sensor calibration or manufacturing information from the sensor electronics unit.
 5. The analyte monitoring system of claim 4, wherein at least a portion of the information is encrypted and is read from a passive tag.
 6. The analyte monitoring system of claim 1, wherein the first communication protocol has a first communication range and the second communication protocol has a second communication range, and wherein the second communication range is shorter than the first communication range.
 7. The analyte monitoring system of claim 1, wherein the selected at least one of the one or more commands is a retrieve data command.
 8. The analyte monitoring system of claim 1, wherein the display device is configured to present a user interface displaying information associated at least with the second portion of the sensor information received from the sensor electronics unit.
 9. The analyte monitoring system of claim 1, wherein the display device is configured to present an alarm based at least in part on the first portion of the sensor information received from the sensor electronics unit.
 10. The analyte monitoring system of claim 1, wherein the display device is a mobile phone or a medical receiver.
 11. In an analyte monitoring system comprising an analyte sensor configured to generate sensor data indicative of analyte levels, a sensor electronics unit communicatively connectable to the analyte sensor, and a display device, a method of using the system to monitor analyte levels of a subject, the method comprising: transcutaneously implanting the analyte sensor; selecting a wake command for the sensor electronics unit; waking up the sensor electronics unit from a low power mode by transmitting the selected wake command from the display device to the sensor electronics unit via a first communication protocol, wherein the first communication protocol uses a Near Field Communication (NFC) transceiver; selecting a retrieve data command for the sensor electronics unit; retrieving sensor data from the sensor electronics unit by transmitting the selected retrieve data command from the display device to the sensor electronics unit via the first communication protocol; establishing a communication channel via a second communication protocol between the sensor electronics unit and the display device, wherein the second communication protocol uses a Bluetooth transceiver; and transmitting sensor data from the sensor electronics unit to the display device via the second communication protocol; wherein the retrieved sensor data via the first communication protocol is being used to display information associated with the sensor data on the display device, and wherein the sensor data transmitted via the second communication protocol is being used to generate alarms on the display device.
 12. The method of claim 11, wherein the first communication protocol has a range of 10 cm or less, and wherein the second communication protocol has a range of 30 feet or more.
 13. The method of claim 11, wherein the low power mode is a sleep mode or a shelf mode.
 14. The method of claim 11, comprising holding the display device within 10 cm of the sensor electronics unit when transmitting the wake command from the display device.
 15. The method of claim 11, wherein the establishment of the communication channel via the second communication protocol includes using authentication information related to the sensor electronics unit.
 16. The method of claim 11, wherein the first communication protocol has a first communication range, wherein the second communication protocol has a second communication range longer range than the first communication range. 